Android Tech Stack Overview
Article Summary
Wahib-Ul-Haq from Freeletics opens the vault on the complete Android tech stack powering four production fitness apps. This is the kind of transparency engineering teams rarely share publicly.
Freeletics manages four separate Android apps (Bodyweight, Running, Gym, and Nutrition) that collectively serve millions of users. The team shares their entire tech stack, from build tools to third-party libraries, including what they're actively replacing and why.
Key Takeaways
- Replacing Guava with IxJava and Arrow to reduce monolithic dependencies
- RxJava ecosystem (RxAndroid, RxBinding, RxRelay) powers reactive architecture
- Moving away from DaggerMock as newer Dagger versions solve same problems
- Always compile with latest Android SDK, Gradle, and Support Library versions
- Five criteria for evaluating third-party libraries: community size, longevity, license, maintainers, battle-testing
Critical Insight
A production-tested Android stack spanning 40+ libraries with honest insights about what's working, what's being replaced, and the decision framework behind each choice.
