Share this page!
Android GDE and Android developer @Plaid | Public Speaker | Blogger | Cycling | Lego | Photography | Dad | https://t.co/C8tvlPt3nv
Add to My Authors
Don't consider this a one off problem: technologies will evolve and new architectures will emerge.
What you really want to do is ensure you can easily experiment with any new tech moving forward.
How will you achieve that? 1/4
A solution would be to modularize and splitting your app in multiple activities.
This allows to (in an extreme case) have a different architecture or tech per module. And you can easily experiment and revert (or keep) the changes when the result isn't what you expected.
This means we should fundamentally let go of the idea of code/architecture/technology consistency across our app.
Even though an engineering dream, there is zero user value in achieving this and migrating things that aren't broken would be prohibitively expensive/risky.
Read 4 tweets