What is an early release edition?
This book is a work in progress, each chapter is released one by one. If you buy the book today, you will be able to read all finished chapters. Once the book is finished, you will get the definitive, edited, book containing all chapters.
What is System Design, is it UI related?
System Design is about technical design. It's about coming up with all the components, API's, and architecture necessary to make a mobile app work. This book will cover the technical design of various components across multiple abstractions and domains.
Is there UI in this book?
This is not a traditional "UI Book" where we cover components and how to style them.
However, the book does cover many important topics related to UI. Such as creating a design system, delivering reusable components, component abstractions, and how to reason about UI architectures.
Is this book focusing on interviews or building an app?
It assists you with both. In this book we'll go over the processes of turning requirements into a robust feature all the way to a modular codebase. Along the way you'll learn mental models that you can apply to your own application and interviews.
This book is not a template to common approaches however. The books' aim is to give you tools so you can solve any problem, not just pre-rehearsed problems.
This way, you can handle any problem that's thrown at you during the system design interviews.
Is this book for Android, Flutter, or iOS engineers?
All mobile engineers! That includes Android, iOS, Flutter, and Hybrid solutions such as React Native.
The book uses iOS and Swift as a vehicle to explain concepts and best practices. Where necessary, the book explains specific Swift keywords.
If you’re Android engineer: Rest assured that Swift reads similar to Kotlin in many ways. With little effort, you'll be able to understand the Swift code examples.
If I already make apps, is this book for me?
Absolutely. The book assumes you're already a developer working on apps, or about to become one. If you’re a senior or junior engineer, then this book is written for you.
I have never even made an app, is this book for me?
The book is aimed at people that have at least some experience in the app-development world.
However, if you've never made an app before, this book will show you what the process entails.
Is this an eBook or printed book?
This product is an eBook. Offered in both ePUB and PDF formats.
Will there be a printed book version?
It is being considered. But the initial goal is to make the eBook available first.
Is this a programming book?
Sort of, but not really. The book covers the process of developing a mobile application. However, it's not a "code book". The book uses Swift to show concepts and how to implement something on a code-level. But it won't show you how to make a complete app from scratch.
It uses code as a vehicle to explain ways of thinking and how to get things done. But this book is more about mental models and avoiding pitfalls. It's about making better choices at every step of the process. From a requirement to a full-fledged, tested, implementation.
What does the subtitle “Resourceful engineering" entail ?
Developing a mobile application has a wide range of topics, from building a small view to maintaining a giant modularized application using a variety of tooling. The term "system design" can encompess even more, from interviews, to architectures, to shared code solutions such as hybrid, a Rust core layer, or Kotlin Multiplatform.
With Resourceful Engineering we refer to a very common, yet local, process in an app codebase, which is 'getting requirements and having to deliver a solution, features, and various components'
In reality, this means you have to move forward despite not knowing all the answers. Making strong choices with limited information is key.
To be resourceful means to be making the best out of the situations with the limited resources that you have.
In this case, that means you will learn to make good decisions at each step of the feature development process. During this process, we’ll try to get all the answers, find the hidden details, and work in such a way, so that our code can adapt to new (unforeseen) requirements.
Help, I can’t afford this book!
If you’re a student or in an unemployed situation, contact me at [email protected], and we can talk options and discounts.
What if I buy it and don't like it?
Send an email to [email protected] within 15 days from the purchase and you will get a refund. No questions asked.
