Clean Mobile Architecture

Clean Mobile Architecture

ISBN: 6188600731

ISBN 13: 9786188600737

Publication Date: April 09, 2022

Publisher: Petros Efthymiou

Pages: 300

Format: Hardcover

Author: Petros Efthymiou

4.46 of 28

Click the button below to register a free account and download the file


Download PDF

Download ePub

*Disclosure:“This post may contain affiliate links and I earn from qualifying purchases”.

“A practical handbook that will provide tremendous help while designing the codebase of your mobile app” —Jovche Mitrejchevski, Software Craftsman

“Provides a carefully balanced view on designing, and growing, an app's architecture in line with the size and requirements of the codebase. A very helpful tool to make more practical sense of how an app's architecture can (and should) evolve over time.” —Donny Wals, iOS consultant & author

—————————————————————————————————————————

The long-awaited book tailored to the architectural needs of Mobile Applications. Clean Architecture is by now a standard in Mobile development. It is listed in every job ad and is assessed in every technical interview. Particularly for senior, architect, and lead positions.

Most software books are written with Backend systems in mind. While the software basics are common, the details differ. And details are crucial. Translating their wisdom into Mobile codebases requires effort and often includes several unsuccessful attempts. This is the one book you need to properly architect Mobile apps. It is platform-agnostic and includes coding samples of both Android & iOS. Read it, and you’ll learn how to:

• Architect your mobile application by Clean Architecture.
• Apply the S.O.L.I.D principles.
• Leverage Reactive Programming & MVI.
• Draw proper architectural boundaries.
• Define adequate testing strategies.
• Leverage Evolutionary design and increase agility.
• Identify when Clean Architecture is needed and when simpler approaches work better.

“Best practices” don’t exist. Some practices solve specific problems while introducing problems that didn’t exist before. What works for a startup doesn’t work for an enterprise app, and vice versa. This book goes the extra mile to clarify when each practice is helpful. And most importantly, when to avoid it.

The book doesn’t only stick to theory. It includes several repos with sample apps that put everything into practice. Theory backed up by practice is called experience. That’s what makes an architect.