The brave new world of the Huawei divorce from Google - HMS and beyond!

Presentation done for Droidcon EMEA - lightning talk about how HMS impacts the future evolution of the Android Development world. Also looked at some other interesting parts that will fill this landscape in future.

Transcript

1. The brave new world of the Huawei divorce from Google - HMS and beyond! Thean Hoogenboezem @TheanHoogenboe1 Mobile Engineering Lead
2. Introduction - Thean Hoogenboezem
3. Android - Humble beginnings • Mobile OS - November 2007 ◦ Modified version of Linux kernel ◦ Open source software - Apache License • AOSP developed by the Open Handset Alliance ◦ Commercially sponsored by Google • First commercial Android device shipped September 2008 ◦ HTC Dream also known as the T-Mobile G1
5. Android OS - Dream Worldwide • Standardised Experience • Running on multiple devices • From Multiple device manufacturers • Utilising Google Mobile Services (GMS) • Apps distributed by Google Playstore
6. Android OS - Vendor Dream AOSP as foundation • Custom Experiences ◦ SAMSUNG Experience - Overlay ◦ Xiaomi MIUI - Android Based OS ◦ Huawei EMUI ◦ Color OS - OPPO ◦ FireOS - Amazon ◦ Many more • Build Value Added Services • Utilise GMS Ecosystem
7. Android Smartphones - last decade • Shipped with pre-installed proprietary software • Google Mobile Services (GMS) ◦ Android Smartphones Running GMS - 70% • Vendor ◦ Custom Experiences ◦ Value added services
8. Fragmentation
9. Fragmentation Simplification • Standardisation ◦ Kotlin ◦ Material Design ◦ Android JetPack ◦ Stable ABIs for Android Kernels • Faster Deprecation of older API’s ◦ Minimum requirement of API 26
10. The Divorce - Google and Huawei
12. What is HMS and how does it fit in? • Huawei Mobile Services ecosystem ◦ Distribution ◦ Cloud storage ◦ Cloud based capabilities ◦ Replaces Google Mobile Services on Huawei Devices • Huawei’s roadmap is to be independent • Intrinsic puzzle piece to the future of landscape
13. HMS Core • App Services - Account, Location and Messaging • Media - Camera and Video • Graphics - Animation and Gaming • Smart Device - CaaS, Cast, Share and Wear • Security - FIDO, DataSecurity • AI - ML • Many more
14. HMS - Huawei • Pros ◦ Own cloud service ecosystem ◦ Improved value added services ecosystem ◦ Scaling developer community ◦ AppGallery distribution Grows • Cons ◦ Customers not wanting to leave GMS ecosystem ◦ Losing customers for lack of support of existing ecosystems
15. HMS - Device users • Pros ◦ Better value added services ◦ Better customised user experiences ◦ Innovation from re-implementing • Cons ◦ Losing cloud history or data from GMS ◦ Losing access to some really awesome Google services ◦ No Google Satellite view equivalent for now
16. HMS - Companies • Pros ◦ Potential new customers ◦ New innovative capabilities • Cons ◦ Losing market share - if not supported ◦ Development investment required ◦ Additional store listing ◦ User experience on Huawei devices for GMS capabilities ▪ Need to port implementations to support ▪ Not everything will work better or the same ▪ Data loss on features linked to GMS capabilities
17. HMS - Devs and teams • Pros ◦ New ▪ Skills to learn ▪ Reinvented Innovation partner ▪ Career paths ▪ Dev Community ◦ Opportunities to innovate solutions for both ecosystems ▪ Non GMS ▪ Non HMS
18. HMS - Devs and teams • Cons ◦ Additional support requirements ▪ Development ▪ DevOps ▪ Store Listings ▪ Testing ◦ HMS services might not offer the same capabilities as GMS ◦ Losing out on great services offered by Google - GMS and Firebase ◦ More Fragmentation in supporting multiple cloud and value adding ecosystems
19. HMS - Third Party Libraries/Products • Pros ◦ Non GMS service offering the same capabilities will gain popularity ◦ New possibilities on how to bundle capabilities/services ▪ Supporting both HMS and GMS ▪ Not tied to either HMS or GMS • Cons ◦ Requirement to support equivalent capabilities with HMS as provided by GMS ▪ Troublesome ◦ Pressure to support HMS equivalent capabilities
20. HMS - Google • Pros ◦ Brand loyalists of GMS ecosystem will stick with GMS supporting devices • Cons ◦ More fragmentation challenges in dev community ◦ Losing developer advocates to Huawei ◦ Losing cloud service customers to HMS ▪ Existing ▪ New ◦ Market share in cloud based services is being challenged
21. HMS - Mobile dev landscape • Pros ◦ Broadening landscape creates new opportunities • Cons ◦ Divergence ◦ Fragmentation ◦ More aspects to consider and understand
22. Next Chapter - OS of the future? • Based on growing market requirements and expectations • Battle is on for the next generation OS • Not an easy task • Yet an important milestone • Who are the contenders?
23. HarmonyOS • Despite AOSP being open source • HMS support ◦ Sets a foundation for road to HarmonyOS • Growing Huawei device user base - without GMS ◦ Will have the option to migrate to HarmonyOS as soon as later this year ◦ Diverging further from Android and Android dev community
24. HarmonyOS? • Future Proof Distributed OS ◦ Micro Unix kernel • All scenario experience • Development Language ◦ Java ◦ XML ◦ Hamony Markup Language (HML) • Apps will be able to run on multiple devices • Devices will share apps, data and capabilities ◦ IoT capabilities
25. HarmonyOS App dev IDE Limitation...
26. Google Fuchsia • Designed for security and privacy ◦ Kernel primitives exposed as object capabilities • Designed to be updatable ◦ Combines components delivered as packages ◦ Packages designed to be updated independently ◦ Packages designed to come and go to device as required ◦ Software always up to date • Designed for performance ◦ Asynchronous communication ◦ Avoids GC in core OS
27. Google Fuchsia • Designed to be language and runtime agnostic ◦ Supports multiple runtimes and languages ◦ C++, Rust, Flutter and Web • Open Source ◦ BSD/MIT-style open source licenses ◦ Inclusive community ◦ Contributions ▪ High quality ▪ Well tested
28. Google Fuchsia is not? • Not based on Linux ◦ Own kernel Zircon - evolving from LittleKernel • Not a microkernel ◦ Does not strive for minimality ◦ Focus on security privacy and performance • Not a user experience ◦ Not tied to specific end-user experience ◦ Developer experience exists • Not a science experiment ◦ Goal - power production devices and products - used by business critical applications
29. Tizen?
30. Ideal Future OS? • Distributed • Language and runtime agnostic • Performant • Secure and Private • Updatable • Development and Developer Friendly • Market Accessible • Compatible with AOSP and Android ecosystem
31. PayTM - Another Store? • This week PayTM launched a mini app store to challenge Google’s Billing Policy in India • As a result Google had to postpone the billing policy until 2022 • What further evolution will come from having another store? • PayTM is already an SDK included in many apps to perform payments and offer a lot of capabilities unrelated to Google ◦ India remains a massive market to reach
32. Conclusion - HMS and Beyond! • Huawei ◦ HMS is rolling out and a lot of organisations are updating and deploying apps to AppGallery ◦ HarmonyOS is potentially coming later this year • Google’s future OS Fuchsia will follow soon after ◦ Does this mean Android is going anywhere yet? • Diverging App Stores and additional fragmentation will shape this market further • Operating systems of the future?
33. Questions?
34. Thank you!