Monolithic application, it's not automatic
summary
An Android app with 200k lines was restructured into a main app plus several small specialty apps to reduce coupling while keeping a seamless user experience. Data and files remain in the main app and are shared to child apps through ContentProvider/ContentResolver and Intent routes protected by signature permissions; a single sign-on is implemented by exposing a file and DB session with timestamp checks so child apps can trigger and resume the main app’s login activity. The implementation relies on shared libraries for resolvers and Intent contracts and discusses lifecycle and testing tradeoffs.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:36Use case
- 4:14N-Applications for N-Businesses
- 8:57Technical solutions
- 11:58Concepts
- 21:39Scenario
- 29:27Possibilities
- 34:12Other uses
related talks
39mScaling an Android App from 1 to 100 developers with modularization.
45mArchitecture for AppBundles
40mModularizing Android Applications
54mXfinity Connected Living: building really, really big android apps
35mArchitecture for App Bundles
40mScaling Android Apps
41mWrite once, ship multiple times
49mBuilding for the future at Snapchat