Building Multiprocess Android Applications
summary
Life360 keeps a multiprocess architecture to isolate the sensor-backed foreground service and reduce crashes and security risk, and engineers build a Kafka-inspired mobile event system called EventsKit that uses SQLite + intents + content provider for persistence and IPC. Each topic lives on exactly one process and a multiprocess resolver routes publishes by sending broadcasts to the owning process while subscribers query that process via a content resolver, avoiding data duplication and keeping IPC rare; this is running in production.
AI-written summary · about
chapters (7)
- 0:00Introduction and overview
- 1:14Why multiprocess on Android
- 2:57Pros of multiprocess architecture
- 6:58Cons and challenges
- 9:06Interprocess communication methods
- 20:18Life 360 event streaming system
- 27:33Alternatives and summary
related talks
17mBest Practises for Android Development as a Daily Business
16mWhy do I have more than one Application instance?
40mScaling Android Apps
28mBuilding an app for the Multi-Device world
52mmulti-module Android application
39mScaling an Android App from 1 to 100 developers with modularization.
32mInside Android: Context, Binder IPC, Zygote
27mBuild effective OEM-level apps on Android Things
