What everyone can learn from building a framework
summary
Built a reusable Android gaming framework called AGF framework that produces MVP apps by composing tested components and features, backed by a small AGF backend that maps provider APIs to a single universal object. Designers push brand values via Figma design tokens, QA uses a QA playground app to verify every component/feature configuration once, and internals stay hidden behind single entry points. Pain points: composition locals break previews, integration tests require heavy mocking, publishing modules creates multiple Gradle imports, but the approach ships and speeds time to market.
AI-written summary · about
chapters (19)
- 0:00Framework building challenges
- 3:38Frameworks vs white labels
- 5:04Figma integration for designers
- 7:58QA testing framework scalability
- 10:49Efficient framework dependencies
- 12:52Backend middleman for providers
- 14:38Client app access and security
- 16:54Data layer and design tokens
- 19:47Performance pitfalls in theming
- 22:01Unit vs integration testing
- 24:06Component layer as Lego blocks
- 25:34Composition locals for theming
- 28:23Navigation in framework features
- 31:41Client navigation responsibility
- 33:29Custom scaffold for UI control
- 36:22Best practices conflicts
- 37:46Imposter syndrome in development
- 40:14Agile adaptation and deprecation
- 40:56Creative solutions for frameworks
related talks
17mBest Practises for Android Development as a Daily Business
40mGrowing Pains: Scaling and Re-architecting Apps Under Fire
42mBuilding Scalable Mobile Projects: Fast Builds, High Reusability and Clear Ownership
40mApp Development - Pragmatic Best Practices
54mThe Golden Principles of Software Architecture Applied To Kotlin Multiplatform
40mCase Study- How Android Platform @ Reddit learned to stop worrying and embrace DevX
36mBuy a Plunger Before You Need a Plunger: Scalable, Flexible, Modular, Preventative Architecture
17mStructuring modules in an Android app project