What everyone can learn from building a framework
summary
An internal Android framework called AGF reduces time-to-MVP by shipping reusable components and features, using a Figma design tokens with modes pipeline to generate theme values, and a central AGF backend mapper that converts provider responses into a universal object per platform. QA gets a QA playground app that exercises every configuration so components are tested once. Practical pain points: multi-module publishing inflates Gradle imports, composition locals break preview tooling, and integration tests are expensive so the team defers them while accepting some pragmatic anti‑patterns that currently work.
AI-written summary · about
chapters (20)
- 0:00Framework building lessons
- 1:09Framework building challenges
- 3:38AGF framework design
- 5:04Figma integration workflows
- 7:58Reusable component testing
- 10:49Scalable framework architecture
- 12:52Backend provider abstraction
- 14:38Securing framework internals
- 16:54Framework data layer
- 18:21Figma to framework tokens
- 20:53Component rendering pitfalls
- 22:01Testing framework strategies
- 24:06Material Design composition
- 26:57Compose preview limitations
- 29:07Framework navigation handling
- 33:29Custom scaffold design
- 36:22Framework best practices
- 37:46Impostor syndrome in framework dev
- 40:14Agile framework problem solving
- 42:02Framework takeaways
related talks
32mBuild a modular Android app architecture
40mModularizing Android Applications
30mModular Android Development
37mA Complete Journey of Android Modularisation
27mModularising the right way
37mForging the path from monolith to multi-module app
40mGrowing Pains: Scaling and Re-architecting Apps Under Fire
41mWrite once, ship multiple times