Android development for FINN and profit
summary
FINN runs Android apps since 2012 with ~40% of traffic on native apps and a team of ~10 Android devs; codebase is ~37% Kotlin and uses Retrofit/OkHttp, Jackson, RxJava, Toothpick DI and a modified Flow for a single-activity architecture. Backend is ~500 microservices; the team moves from a presentation-heavy proxy to a gateway pass-through and from HTML-like page payloads to pure data, splits the app into ~25 modules, replaces a 600-line Rx image loader with Glide, and serializes navigation stacks to disk.
AI-written summary · about
chapters (13)
- 0:00Introduction and welcome
- 1:14About FINN and its apps
- 3:03Company mascot and history
- 5:59App architecture overview
- 8:12Why Kotlin for Android
- 14:20Lessons learned from development
- 17:59Proxy to gateway architecture shift
- 20:33Object page format challenges
- 26:20Single activity and navigation
- 30:15Modularization of the app
- 33:53NIH syndrome and code readability
- 36:54Future directions and tech
- 41:56Summary and takeaways
related talks
49mBuilding for the future at Snapchat
01h 13mModern Android development
58mModern Android Development
54mXfinity Connected Living: building really, really big android apps
51mModern Android Development
39mScaling an Android App from 1 to 100 developers with modularization.
48m36･15 Cash App
38mAchieving Maintainability: Best Practices for Keeping Your Android App Up-to-Date