![]() ![]() The migration did help with Android's fragmentation woes, but it also has led to a monopolistic universe where the exclusion of Google Play Services could handicap the entire experience of an Android smartphone. This allowed app developers to build experiences that would function in the same manner across different Android versions. Two of those three situations are to the detriment of the app developer, and exploring an alternative to reduce the over-reliance on GMS might be in the better business interest of the developer. For affected users, this meant that several of their apps would remain broken until the trade situation was resolved, or the app developers explored alternatives, or the user explored alternative apps. This meant that developers who exclusively relied on GMS for functionality within their apps lost access to the tools that made those functions possible on future Huawei devices. While Huawei could still continue using Android because of the open-sourced nature of AOSP, it couldn't use the proprietary Google Mobile Services (GMS), and by extension, Google Play Services on the Huawei Mate 30 Pro. ![]() ![]() The other major factor that also needed to be addressed is the fact that a lot of Android apps, including Google Apps, rely on a closed set of APIs to function - APIs that separated AOSP's Android from Google's Android, coming in the form of Google Mobile Services and Google Play Services. But distributing apps solves only part of the equation. The Huawei AppGallery offered end-users and app developers an alternative to the Google Play Store, functioning as a medium to distribute and maintain Android apps. Thankfully, Huawei had the foresight to work on some of its own solutions long before the unfolding of any trade politics.
0 Comments
Leave a Reply. |