What Is the Best Architecture for Android Apps That Integrate Closely with External Devices?
summary
An Android taxi app must integrate tightly with external hardware (meter buttons, BLE loggers, and server pushes). The team defines meter protocols as interfaces, supports both BLE‑logger and Bluetooth Classic meters, replaces messy Rx code with a dispatcher/store (Flux) flow, inserts a state machine to block invalid meter transitions, publishes a small nested-state DSL as OSS, modularizes core vs UI for tablet/phone development, and uses a BLE‑logger abstraction plus Flux + state machine to make the service reliable.
AI-written summary · about
chapters (10)
- 0:00Android device-integrated architecture
- 3:24Mob taxi dispatch system
- 10:03Service growth challenges
- 12:39State management with DSL
- 14:30Parallel phone and tablet dev
- 16:46GUI and system architectures
- 21:59Final architecture design
- 25:01Data flow with meter changes
- 27:58State machine implementation
- 30:51Summary
related talks
15mArchitecting Amp: Android integration with embedded systems
45mScaling Architecture at Lyft
42mDeep Android Integrations
17mBest Practises for Android Development as a Daily Business
39mTalking to your bike and other devices (wait, what?)
36mModern Architecture of Android Apps — Archetype
18mArchitecture is vital to build an app. But what is that concretely?
31mAn introduction to Bluetooth mesh for Android developers