WhoBuilt

From Fragmentation to Unity: The Role of OMH in Mobile Development

Sep 26, 2024· 40 min· 244 views·Watch on YouTube

Speakers

Preston Lau, Open Mobile Hub Technical Steering Committee chair, presents OMH’s approach to mobile platform fragmentation at a Callstack conference, then Diego Zuluaga, Open Mobile Hub’s Technical Solution Engineering lead, explains the architecture and demos its integrations.

The mobile fragmentation problem

Lau describes two challenges: keeping user experiences consistent across devices and avoiding duplicated development work. Android devices may use Google Mobile Services, AOSP without GMS, or manufacturer-specific software, alongside iOS and HarmonyOS. Apps that depend on GMS can lose login, maps, storage, or payment features on devices without it.

How OMH routes services

Open Mobile Hub provides a shared library that checks which services are available at runtime. It uses GMS when present and can use alternatives, such as web-based Google authentication or OpenStreetMap for maps, when GMS is absent. Lau says OMH 1.0 included authentication, maps, and storage, and announces the React Native modules in OMH 2.0.

A shared interface with provider plugins

Zuluaga explains that apps can become tied to Google SDKs, while adding manufacturer and independent provider SDKs can increase app size and make provider changes require code changes. OMH uses a two-layer design: common interfaces for maps, authentication, and storage, with separate provider implementations. Its plugins are extensible, and the same approach supports native and cross-platform apps.

Maps and storage across devices

The maps demo shows provider switching and features including markers, polylines, polygons, and location sharing. Providers do not have identical capabilities; for example, Street View is not available across providers, and some styling features are provider-specific. The storage demo covers Google Drive, OneDrive, and Dropbox, including sign-in, browsing, file creation, downloads, and metadata.

Release scope and community plans

Zuluaga highlights OMH’s support for non-GMS devices, multiple service providers, and an extensible design. The team is seeking community feedback and exploring Expo compatibility, as well as future support for Flutter, HarmonyOS Next, ads, and payments. Lau says the Technical Steering Committee meets monthly and invites developers to contribute through the project’s GitHub discussions.

Takeaways

  • Check whether core app features depend on GMS before targeting AOSP devices without it.
  • A provider interface can make it easier to switch services without rewriting app logic.
  • Plan for provider feature gaps; a shared API does not guarantee identical capabilities.
  • OMH’s examples show how authentication, maps, and storage can be tested across different device ecosystems.
  • Review OMH’s provider support and Expo plans against your app’s platforms before adopting it.

Mentioned in this talk

Search inside this talk

What was claimed 17

Related talks