App Development - Pragmatic Best Practices
summary
Survey of 150 Android devs finds top pain points: architecture, Android lifecycle/configuration quirks, and testing. Advice is concrete: enforce single responsibility and layer apps into view/logic/data with clear interfaces, use dependency injection for testable wiring, treat disk as the single source of truth (network writes disk, UI reads disk), use ViewModel/LiveData or auto-dispose Rx to avoid lifecycle bugs, persist minimal IDs in saved state for restarts, weigh Retrofit/RxJava/Dagger benefits and learning costs, and write tests before refactoring.
AI-written summary · about
chapters (10)
- 0:00Introduction to app practices
- 1:19Why architecture matters now
- 8:25Separation of concerns basics
- 12:38Dependency injection principles
- 17:42Layered architecture explained
- 18:03Android lifecycle solutions
- 25:03Handling config changes
- 29:58Screen and hardware fragmentation
- 32:50Favorite libraries and costs
- 37:48Refactoring and testing importance
related talks
17mBest Practises for Android Development as a Daily Business
31mPatterns for Safe Refactoring of Android Apps
29m10 Ways To Improve Your Android App Performance
42mIngredients for a healthy codebase (en)
32mEffective Android Architecture
49mBe Like Water: Keeping Up with Android
45mFor Beginners and Career Changers: Android App Development Today and Key Points in 40 Minutes
41mHow to Really Test an Android Application