![Building Mobile Apps at Scale: 39 Engineering Challenges](https://d3k2uuz9r025mk.cloudfront.net/media/image/cc/7d/e9/1673692821_271834534535_600x600.jpg)
Building Mobile Apps at Scale: 39 Engineering Challenges
Kurzinformation
![Natural](https://shop.studibuch.de/media/image/c4/23/50/Buch-Vorteil.png)
![Coins](https://shop.studibuch.de/media/image/74/b1/94/Lieferung-Vorteil.png)
![Check](https://shop.studibuch.de/media/image/a1/0b/2c/Muenzen-Vorteil.png)
inkl. MwSt. Versandinformationen
Artikel zZt. nicht lieferbar
Artikel zZt. nicht lieferbar
![Zahlungsarten](/media/image/d6/9c/c0/Payments.png)
Beschreibung
While there is a lot of appreciation for backend and distributed systems challenges, there tends to be less empathy for why mobile development is hard when done at scale.This book collects challenges engineers face when building iOS and Android apps at scale, and common ways to tackle these. By scale, we mean having numbers of users in the millions and being built by large engineering teams.For mobile engineers, this book is a blueprint for modern app engineering approaches. For non-mobile engineers and managers, it is a resource with which to build empathy and appreciation for the complexity of world-class mobile engineering.The book covers iOS and Android mobile app challenges on these dimensions:Challenges due to the unique nature of mobile applications compared to the web, and to the backend.App complexity challenges. How do you deal with increasingly complicated navigation patterns? What about non-deterministic event combinations? How do you localize across several languages, and how do you scale your automated and manual tests?Challenges due to large engineering teams. The larger the mobile team, the more challenging it becomes to ensure a consistent architecture. If your company builds multiple apps, how do you balance not rewriting everything from scratch while moving at a fast pace, over waiting on "centralized" teams?Cross-platform approaches. The tooling to build mobile apps keeps changing. New languages, frameworks, and approaches that all promise to address the pain points of mobile engineering keep appearing. But which approach should you choose? Flutter, React Native, Cordova? Native apps? Reuse business logic written in Kotlin, C#, C++ or other languages?What engineering approaches do "world-class" mobile engineering teams choose in non-functional aspects like code quality, compliance, privacy, compliance, or with experimentation, performance, or app size? von Orosz, Gergely
Produktdetails
![](https://d3k2uuz9r025mk.cloudfront.net/media/image/b1/82/59/handgeprueftSiegel.png)
So garantieren wir Dir zu jeder Zeit Premiumqualität.
Über den Autor
- Hardcover
- 268 Seiten
- Erschienen 2022
- Packt Publishing
- Kartoniert
- 414 Seiten
- Erschienen 2014
- Apress
- Kartoniert
- 272 Seiten
- Erschienen 2017
- Kogan Page
- Taschenbuch
- 304 Seiten
- Erschienen 2021
- Addison Wesley
- Hardcover
- 406 Seiten
- Erschienen 2023
- Packt Publishing
- Kartoniert
- 1106 Seiten
- Erschienen 2019
- Wiley-VCH
- Hardcover
- 284 Seiten
- Erschienen 2018
- Packt Publishing
- Taschenbuch
- 282 Seiten
- Erschienen 2021
- Razeware LLC
- Taschenbuch
- 325 Seiten
- Erschienen 2022
- Manning Publications