Building Apps that Scale
summary
Concrete practices: write KDoc comments with use cases so hover text explains KDoc, stop clever one-liners, organize code by feature packages, and add unit and Android lifecycle tests. Performance tips: aim to keep cold start under 5s, avoid heavy work in Application or MainActivity, update UI optimistically, and cache API responses locally with Room/SQLite. Backend choices: use AWS Amplify (Auth, Storage→S3, DataStore + AppSync syncing to DynamoDB) and leverage the free tier and docs/Discord for setup.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:32Scaling apps beyond silver bullets
- 4:19Documenting code with KDoc
- 9:31Avoid clever code for clarity
- 11:41Organizing feature-based folders
- 15:36Testing code to prevent outages
- 20:18Optimizing app start time
- 25:33Making interactions instant
- 27:43Storing data locally
- 30:18Choosing backend resources
- 36:17Resources and closing
related talks
17mBest Practises for Android Development as a Daily Business
40mApp Development - Pragmatic Best Practices
32mBuilding Apps with an API-based Backend
33mGuide for lazy developer
19mBuilding for Scale: How not to get Caught out at Global Launch
49mScalable Best Practices for Your Development Team
27mStop wasting time: 3 ways to build web applications faster and better
31mBuild apps for the next billion users