Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Adopting Huawei Mobile Services

Adopting Huawei Mobile Services

Common questions - what, how, why?
What are Huawei Mobile Services(HMS) and Huawei App Gallery? How to apply to our application in a most efficient way. Reviewing alternative libraries of Google Play services from HMS. Why do we need to support another platform as a business and what are the best ways to overcome this difficulty? Is it HMS or platform-agnostic 3rd party services like OpenStreetMaps? This talk briefly covers all of these topics

Merab Tato Kutalia

November 13, 2021
Tweet

More Decks by Merab Tato Kutalia

Other Decks in Programming

Transcript

  1. What are Google Play Services? Google Play Services is a

    background service that runs on Android, which in turn helps in integrating Google’s advanced functionalities with other applications. It is also used to update Google apps. Google’s fragmentation issue is tackled using Google Play Services. It ensures that even older versions of Android enjoy the latest features provided by Google.
  2. Google Play Services • Google Maps API • Location APIs

    • Google Drive API • Google Play Game Services • Google Cast • Google Mobile Ads • Google Login • and many more (Fit, Wallet, Protect…)
  3. Why and when should we care? • Our app uses

    Play Services exclusively for Feature X • 3rd party services that use Google Play Services • Cover more users • Get better insights and statistics about crashes
  4. Adoption • Use platform agnostic services (Not always ideal) •

    Adopt Google Mobile Services and Huawei Mobile Services separately Pain: • Handle each store independently, track policy changes and compatibility • Handle multiple APKs • Handle CI/CD issues
  5. Platform agnostic services Pros and cons • Offers same UX

    across the devices and platforms • Same billing plan • Easy to manage credentials • Fixed APK sizes • Consistent for testing • Single implementation • Not ideal solutions • Vendor lock-in • Not every service has an alternative
  6. Adopt mobile services Pros and cons • Native experience •

    Cover large user base • Always up-to-date • Handle problems independently • Multiple implementations • Different billing plans and quotas • Handling multiple credentials • Sometimes needs extra work to achieve the same UI/UX • Hard to maintain • CI/CD support, PR workflows
  7. Flavors • Each can have its own source sets •

    tests • dependencies https://developer.android.com/studio/build/build-variants https://docs.gradle.org/current/userguide/variant_model.html