Besides, gs can't get up in China, and aab is just air. And domestic machines don't have their own app stores?

In China, it is not domestic adaptation to aab, but domestic adaptation to aab.

The last point is very important!

If apk is banned in the next version of Android, then HarmonyOS can really laugh.

Because at that time, there were only two and a half choices made domestically. First, the old version of Android will maintain itself. Second, cut down the HarmonyOS system. The other half is to maintain the aab version of Android specifically for overseas markets.

But the cost is huge, and it will cause product division, so it is very likely that HarmonyOS system will be cut.

In addition, not only do we have various UI/o, but foreign friends also have their own UI/O.. If HarmonyOS system can be released by the prefix of China and thrown overseas [wit], you know, Android has created a powerful enemy.

Does it matter? Does he mean that apk is not allowed to run? What domestic software has passed the Google platform? Need to use his GMS. Your question is a false proposition. At least for now.

With the blessing of "HarmonyOS System 2.0 is compatible with Android APK application software" and "Microsoft announced that the upcoming Windows 1 1 can directly install and run Android APK application software", Google announced that it would abandon APK and adopt a brand-new AAB application software format, which is somewhat intriguing.

So many people have speculated and polished this matter: "Google intentionally blocked HarmonyOS system and prevented HarmonyOS system from using the Android ecosystem to grow", "Google abandoned APK format and changed it to AAB format, and Windows 1 1 gradually lost its native support for Android software", "Google changed the format of Android application software from APK to AAB format because it didn't want Android to be an accessory of others, but because it didn't want it to be an accessory of others.

It is only a matter of time before AAB format of Android application replaces APK format. The full name of AAB format is android app bundle, which was launched by Google on 20 18. Until now, Google announced: "From August 20021year, new applications need to be bundled with android applications before they can be released on Google Play".

In fact, AAB can be understood as the dynamic packaging of Apk, and AAB completes the dynamic loading by splitting APK, which greatly reduces the volume of application software. For example, the APK project will contain both xxhdpi and xhdpi, or a set of so libraries of x86, arm and arm64bit, which will be loaded into the user's mobile phone. Google Play is based on AAB file processing. We will get your hardware information when downloading the application from Google Play, and then App Bundle will help us assemble an APK. Only the corresponding resources of mobile phone hardware will be eliminated.

The file structures of AAB and apk are basically the same, but the android app bundle splits the resources of APK from multiple dimensions. In this way, Google Play can be dynamically delivered through the android application bundle, and the mobile phone hardware can be given whatever it needs. In addition, android app bundle also supports modularization, which splits an apk into multiple apk and loads it on demand, including C/C++ libraries.

The final result of android application bundle is similar to the plug-in we understand, except that android application bundle needs to be loaded on demand through Google Play.

Google Play cannot be used directly in China, so AAB cannot be used as a distribution method. Iqiyi's open source framework, Qigsaw, is an Android dynamic component distribution scheme realized through android app bundle, which can dynamically distribute components without reloading applications. So don't worry that the Android application bundle can't be used in China. This technology will soon follow up the application market of domestic mobile phone manufacturers. After all, android application bundling is not a dirty secret.

APK is not dead, but it has evolved and split into smaller APK units. This new model undoubtedly greatly reduces the size of the application, so it takes less time to download or install the application on devices with smaller storage space. Android application bundle is open source and backward compatible. Although APK will be divided into many APK, only one APK will be generated per device configuration, instead of using split APK. In the distant future, android application bundle may exist in another form, but not now.

To sum up, friends will think that Google's AAB format has attacked HarmonyOS system and Windows 1 1 until now, and AAB format will not hinder the support of HarmonyOS system and Windows 1 1 for Android applications. The above logic does not conform to Google's open source and open attitude. Google will only develop more novel and innovative things to continue to write its new myths, instead of living in a narrow pattern.

You said yourself that Google abandoned apk for aab. What does this have to do with domestic manufacturers?

Simply put, aab is the file format submitted by developers to google, and apk is the file format downloaded by users from Google Store.

To be exact, aab is a complete package, including resources suitable for all types of hardware, such as Qualcomm adreno gpu driver and ARM gpu mali driver, so aab is a complete package, suitable for all types of hardware.

The normal way to use it is for developers to provide aab packages to Google for review. When a user needs an apk, Google Store will read the hardware information such as the user's mobile phone model, and then package an apk suitable for the user's mobile phone hardware and download it to the user. The apk that users get at this time is the most concise but most suitable version.

It is true that Google abandoned apk and changed to aab, but this sentence is taken out of context. Google's restrictions on aab provided by developers have little to do with ordinary users. You installed apk, but it was optimized by Google.

According to the official report of Android Authority, Google has not completely abandoned APK, but only requires developers to submit all applications submitted to Google App Store in AAB format from August 20021year. But at present, APK applications can still run in the original way. Therefore, domestic mobile phone manufacturers will not have much influence. After all, they don't use Google GSM or Google App Store. Isn't it? However, although there is no impact at present, we still need to pay attention to the following points for the future.

1, is APK really out of date? Microsoft win 1 1 just said that it supports APK. First of all, let's talk about APK, which is the abbreviation of Android Package. Where there is an Android system, there is the shadow of APK. 100% At present, APK is the application used by domestic mobile phone manufacturers. Google suddenly said that it would force developers to use AAB format. Is APK out of date? Recently, Microsoft just announced that win 1 1 system can support native Android applications, and consumers can use it in Microsoft Store and Amazon Store. Judging from this news, APK should not really decline. However, Google has developed a new technology and wants to promote it.

Let's take a look at AAB, a brand-new application bundle launched by Google on 20 18. Google itself claims that this new format of application files will be smaller, easier to control and more convenient. There are already thousands of ABB apps in Google Store. This sounds good news for both consumers and developers. After all, everyone wants the program to be smaller, more efficient and updated faster.

However, Google itself realizes that it is not easy to fully implement AAB at once. After all, APK is still running smoothly, and there are no special problems. Therefore, it can only ask its own app store to use AAB, but can't ask other app stores to support it through GSM or other means. At the same time, Google still retains the function of exporting AAB format to APK. If consumers want to use new applications in AAB format, they can export them to APK. It can be seen that APK still has a market and will not decline immediately. Domestic mobile phone manufacturers will not have any impact for the time being.

2. The mandatory use of ABB by Google Store reflects Google's intention. Since Google has announced that it will use AAB format bundle in its own application market, it naturally has its own small abacus. In addition to promoting the benefits of AAB format, it also tightened the rights of Google App Store. Consumers and developers are tied together by Google App Store, and in the future, Google Store will eventually become an unavoidable entrance. By that time, Google can harvest leeks. This is very similar to Apple's Apply Store.

At the same time, if developers want to satisfy the function of exporting AAB format to APK, it is very likely that they need to provide Google with the signature key of the application. However, developers all know that this application signature key has considerable rights. It is equivalent to authorizing Google to sign applications on behalf of developers. Of course, we believe that Google will not do such unsafe things, but it does not mean that it will not happen.

3, domestic mobile phone manufacturers must have a sense of independent research and development, otherwise they will always worry that although APK will not be abandoned immediately, domestic mobile phone manufacturers can continue to use APK for a long time, but it will eventually be restricted by other manufacturers. If other manufacturers suddenly change their strategies or make big moves, it will still have a great impact on the future. Just like Google's AAB this time, although it will not immediately affect domestic mobile phones, it does not mean that AAB will be popular in the future. After all, the application ecology is the key factor of mobile phones and systems. Therefore, domestic mobile phone manufacturers must plan ahead and have the awareness of independent research and development. Being able to develop independently as much as possible can improve the user experience of your mobile phone, precipitate technology for yourself, and prevent problems before they happen. This is also the starting point for Huawei to insist on self-research in the past.

To sum up, it is a good thing for Google to implement AAB. This may also be good news for consumers. But it may not be good news for domestic mobile phone manufacturers. Although it will not have much impact on APK at present, it will not affect its own market changes. However, with the passage of time, the applied ecology may change to AAB format ecology. Therefore, domestic mobile phone manufacturers must have a sense of independent research and development.

At present, the existing Android system can use APK and AAB installation formats. In other words, APK was not abandoned by Google, but added a better AAB format installation package.

Therefore, at least temporarily, it should not have much impact on the domestic Android application software market. But there are also hidden dangers.

Currently, AAB format is mandatory for Google's own Play Store. In other words, the software uploaded to the Play Store must be packaged in AAB format. However, this mandatory requirement is only useful for the Play Store, and domestic app stores do not have this requirement. And if China people don't go abroad, they probably won't have too many opportunities to get in touch with the Play Store. In this way, Google's AAB installation format can be temporarily ignored.

If we want to guess Google's decision from the perspective of conspiracy theory, it is probably related to Microsoft Windows 1 1 being fully compatible with APK format. It can be guessed that this is a strategy for Google to deal with Windows 1 1. The reason is that Microsoft is not cooperating with Google, but with Amazon in terms of compatibility with Android software. Two competitors cooperate, and Google doesn't respond, which is too numb.

Theoretically, HarmonyOS system is software based on AOSP, so it is compatible with APK format. If Google still attributes AAB to AOSP, then HarmonyOS still has a chance to be compatible with AAB format. But if AAB format belongs to AOSP, then Microsoft still has reason to be compatible with Android applications. Therefore, Huawei's HarmonyOS system is likely to be affected, which belongs to the situation of "the city gate is on fire, and the fish in the pool are affected", but the specific situation continues to look down.

However, don't be surprised if the next version of Xinzhuo system can only use AAB format. By then, domestic software stores should follow up as soon as possible, and various software developers will follow up in time. People will never offend customers. At that time, there must be a solution to meet the needs of our users. However, the HarmonyOS system is even more embarrassing. But other brands that use Android are fine, just continue to unite around Google Android!

In addition to Huawei, brands include but are not limited to Xiaomi, OPPO and Glory. In China, Android is currently being used. It can be said that the impact of this change in Google is extensive and far-reaching.

This wave of Google actually wants to imitate Apple, control the download channels and improve the draw. To put it bluntly, it is to collect protection fees and cut leeks.

Moreover, this move is cruel enough to force software vendors to change the new format, but the format of HarmonyOS system is also adapting. Isn't it time for HarmonyOS system to increase the difference quickly?

This is in line with the extinction of Huawei by the US imperialists!

Therefore, there is no underlying foundation, and it will always be the degree of passive beating. The more developed in the future, the narrower the road for domestic brand mobile phones. Limitations of the underlying system and application channels of software; Hardware chip limitations, etc. We all need manufacturers to seek breakthroughs, and don't be caught by the throat and the lifeline.

We don't know whether Android will continue to be compatible with APK in the future, but we can be sure that all new Android applications in Google Play Store need to use AAB.

But in fact, other distribution channels are not prohibited in the original text. The difference is that you can only use Google's signboard, so domestic machine factories can say that they will not be affected for the time being, and it is hard to say in the future.

So, let's strive for self-improvement quickly.

Isn't this forcing domestic software developers to abandon Android and switch to HarmonyOS system?

Businessmen's considerations are different from those of the public. From the national point of view, our enterprises should unite around the HarmonyOS system, but businessmen will not. They are interested in immediate interests. I want to ask you to abandon Android and embrace HarmonyOS system, and abandon Qualcomm and embrace domestic products. Even if it is more than 20 nanometers, what can it do? Businessmen only hope that enterprises like Huawei can survive this crisis.

Vendors will probably use their own apk instead of Google's own private file format, because they have their own interests, otherwise their software stores will be merged into Google's software stores, which vendors are unwilling to do.