Hey there.
I’m excited to announce that Chapter 15 of the Mobile System Design book is now available! It’s called Delivering self-sufficient features, part III; Making features portable.
If you already own the book, you can grab the latest version (v007) here.
In case you haven’t gotten the book yet, you can find it at www.mobilesystemdesign.com.
Portable features bring us a lot of benefits. First, it allows us to deliver features that can survive UI migrations, such as moving from UI pattern to a new one, or moving from one paradigm to the next.
Besides that, portable features enable us to disconnect a feature from a screen, ensuring it can work in the background.
But perhaps most importantly, portable features allow us to unit-test a larger surface, so that we can rely less on UI Tests or manual verification for the same quality guarantees.
In this newly released chapter, we'll look at how to make features more portable by pushing more logic out of the UI domain into the model domain. We do this by taking a detailed code-level look at how to achieve this.
The book’s roadmap
I wanted to give a heads up about the remaining chapters and align on some expectations.
With the addition of this newly released chapter, the number of chapters is moving from 19 to 20! Originally, the book was planned to have 9 to 12 chapters. But I quickly learned that I want to explain topics more in-depth, which requires more chapters. This is to help readers give a deeper understanding of certain topics.
That does mean that when I hit a large topic, this gets split into multiple chapters. For example, the dependencies topic turned into three chapters (almost four, even). The same goes for the self-sufficient features series.
For instance, I can foresee that once I write about large-scale architectures, I might not fit that in 20 pages, it might turn into multiple chapters. I don’t want to over-promise yet, but my estimate is that the book will grow some more.
Because the book keeps expanding, I am pushing back the estimated release from 2024 to 2025. Not to worry, you will still get continuous chapter releases. You just get more chapters than promised.
Also, it doesn’t mean you have to read all chapters either, you can pick and choose the topics that interest you.
Fun fact, my first book, Swift in Depth consists out of 15 chapters. The same number the Mobile System Design book has now!
Thanks for reading, and see you at the next update.