Open Mobile Hub: Modules for Non-GMS Devices and Beyond

The discussion distinguishes Android Open Source Project (AOSP), which provides the base operating system, from Google Mobile Services (GMS), a separate layer of proprietary services. AOSP can suit single-purpose devices, such as screens in taxis, while other devices may need services for authentication, maps, or notifications. Device makers can also add their own services.

Open Mobile Hub offers a common interface for Android and cross-platform apps to use services from different providers. The goal is to reduce the work of switching SDKs and help apps serve regions where GMS or particular services are unavailable. The initiative is hosted by the Linux Foundation Europe to support open collaboration and neutral governance.

The modules discussed are Maps, Authentication, and Storage. Maps supports Android, React Native, and iOS, with Mapbox, OpenStreetMap, Azure Maps, and Google Maps; Authentication supports OAuth 2.0 providers including Dropbox, Google, Microsoft, and Facebook. Storage connects to services including Google Drive, Dropbox, and OneDrive, using authentication to access a user’s account.

OMH has a native Android SDK layer and a React Native layer built on the native SDKs. Developers add modules through Gradle dependencies and use clients with provider plugins behind them. The shared interface covers common needs, while an escape hatch lets developers access provider-specific capabilities.

The OMH website links to setup guides, samples, documentation, API references, and GitHub repositories. The team welcomes developers and service providers to contribute plugins, report bugs, and share feedback to inform the roadmap. The episode describes some components as ready to use and others as early access.