No Play Services? No worries!
summary
Explains concrete swaps: Firebase Firestore, Auth and Crashlytics work without Play Services but FCM, ads and some ML do not, so replace push with Pushy (MQTT), self‑hosted OpenPush (you build server + client) or RabbitMQ; maps use the standalone Google Maps beta or alternatives like OpenStreetMap and Here SDK (OSM is heavier and less smooth), distribution via F‑Droid, APK mirrors or MDM, install handled with PackageInstaller; GeckoView replaces WebView. Sample apps run and show tradeoffs in size, latency and implementation complexity.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:08Why avoid Play Services
- 4:44Firebase alternatives
- 7:14Push notifications without FCM
- 13:26RabbitMQ for messaging
- 20:26Google Maps replacements
- 25:32Distributing apps without Play Store
- 28:49Building your own MDM
- 32:45GeckoView for web content
- 36:02Q&A and resources
related talks
14mBuild powerful, reliable apps with Google Play services
53mHuawei Mobile Services Vs Google Play Services?
41mWhat's New in Google Play Services
33mMaking Android Apps with Intelligence
49mWelcome & keynote
58mAndroid Protips 3: Making Apps Work Like Magic
49mServices: You Can't Live Without Them, So How Do You Cope?
47mWhat's Wrong with Mobile Services on Android and iOS