We recently did an overhaul for Instacart’s shopper app and committed to using a presenter pattern for this. It turned out awesome! Presenters are not a new concept. They’ve been around since the dawn of software engineering time. But the devil is in the implementation details. If you have an Activity, RecyclerView, Adapter etc. at how many levels would you have the presenter? How does the use of presenters enabled super fast testing? How does the use of presenters enable constantly changing user requirements? We’ll discuss all the juicy war stories in this session
What I learnt using the Presenter pattern
You might also enjoy
- Architecting Android and iOS app features for 2020
- Painless UI Testing
- Agentic coding: a roundtable with industry leaders — Android Dev Summit
- Silicon Valley Senior Android Engineer — interview with CodingWithMitch
- Unidirectional State Flow patterns – a refactoring story
- Supercharging your workflow with App Center and Azure
- Rx by example – Volume 3 (the multicast edition)
- Android Developers Backstage — Episode 69 "IO IO"
- Learning Rx by Example (Part 2)
- Learning Rx by Example (Part 1)