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
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
https://twitter.com/riggaroo/status/1363439716973113344
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. 2/4
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. 2/4
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. 3/4
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. 3/4
So my approach would be:
1. Split your app in several modules and activities
2. Convert a low risk module to learn the tech
3. Convert other modules while adding new user value according to your roadmap (if conversion doesn't add user value, consider punting it)
4/4
1. Split your app in several modules and activities
2. Convert a low risk module to learn the tech
3. Convert other modules while adding new user value according to your roadmap (if conversion doesn't add user value, consider punting it)
4/4
• • •
Missing some Tweet in this thread? You can try to
force a refresh
