From the author of The Pragmatic Engineer blog and The Tech Resume Inside Out

Building Mobile Apps at Scale: 39 Engineering Challenges

Building mobile applications at scale are just as challenging as architecting and operating distributed systems. I know - I've done both for years at Uber. There tends to be little understanding of these problems until coming across them - and even fewer resources to go about addressing them.

The missing guide for building large, iOS, and Android native apps -with the challenges and common solutions across the industry.

Get the book
Building Mobile Apps at Scale

Frequently Asked Questions

Can I share this book with a group?

The book license is for one reader only. Please respect the terms, and do not distribute for others. The book comes DRM-free to make your personal use easy.
Team licenses:

Is there a Kindle or paperback version?

There will be both, following the launch of the book.

I'm not a mobile engineer. Is this book for me?

The book is tailored for software engineers and engineering managers building larger native iOS or Android apps. You might also find this book helpful if you work with teams like this.

Will there be a paper copy of Growing as a Mobile Engineer?

I don't currently have a plan for a paperback for that book. However, by getting the Full Edition, you'll get a PDF, and EPUB and a MOBI version of the book.

image

About the Author

I've been building native mobile apps since 2010: starting on Windows Phone, later on iOS, and Android. Starting from one person apps, I worked with small teams at Skyscanner, to hundreds of engineers working on the same codebase at Uber.

At Uber, I've been part of the Rider app rewrite, Driver app rewrite, both projects involving hundreds of mobile engineers. The apps my team worked on had 100M monthly users in 60+ countries, with several features built for a single country or region.

I’ve been working on this book - originally meant to be a blog article - on-and-off, for over a year. A Twitter post gave the final push to finish the contents off. The contents were too long for a single post. This is how this book was born.

Follow me on Twitter at @GergelyOrosz, connect on Linkedin or reach me at scale (at) pragmaticengineer (dot) com.