Hey there.
I’m excited to announce that Chapter 14 of the Mobile System Design book is now available! It’s called Delivering self-sufficient features, part II; Self-loading features.
If you already own the book, you can grab the latest version (v006) here.
In case you haven’t gotten the book yet, you can find it at www.mobilesystemdesign.com.
This chapter is part of the self-sufficient features series, where it shows you how to make a feature more standalone or self-sufficient.
The reason I am adding this topic to this book, is because it’s tricky to deliver decoupled features without overengineering and introducing tons of interfaces or complexity. But if done right, it brings a ton of benefits. Self-sufficient features allow us to “cut and paste” features around in an application, and even across modules! As a result, we will be more agile when unforeseen changes come up, we can better support deep-linking, and even large-scale app architectures.
Loading data and glueing it to UI is at the heart of our work as mobile engineers. With that in mind, I did not want to make a beginner tutorial “this is how you show data in UI”. I respect that you’re a busy engineer. Instead, I wanted to go deeper and reason about all the micro-decisions and trade-offs to make at every step during this process.
The chapter showcases techniques such as ID lookup, when (not) to use closure dependencies, reasoning about mutation, and what to do if a feature can handle partially loaded data.
You can grab the update (v006) here and find the book at www.mobilesystemdesign.com.
Also, don't forget to check out the Mobile System Design YouTube channel for more valuable content!
Happy coding.