"Clean Architecture for Android" was written to help developers apply Clean Architecture to their projects. The book will explain why Clean Architecture is so valuable. It will demonstrate how you can use this architecture to build more reliable and extensible apps. It will also show you how Clean Architecture helps ensure your projects are easy to maintain. This book will explain the structure and functions at each level of the architecture. It will show you how to integrate Clean Architecture into your project and gradually transition from your current architecture to the new one. Finally, it will demonstrate how to apply the various Clean Architecture concepts by practicing and demonstrating their value. If you are new to creating Android apps, this book will give you the foundational knowledge you need to start creating apps using Clean Architecture. It will walk you through the process of dissecting requirements into the Clean Architecture layers. It will then teach you how to implement every one of these layers. As a result, your development process would speed up in the long run and will produce a high quality product. Having a high percentage of your code tested is also beneficial, which is why in this book you will also learn how to test your app.

• Cover Page
• Title Page
• Copyright Page
• Dedication Page
• About the Author
• About the Reviewer
• Acknowledgement
• Preface
• Errata
• Table of Contents
• 1. Introduction
  • Structure
  • Objective
  • Conventions
  • Clean Architecture
    • Clean Architecture vs MVVM
    • So now I must rewrite my project
    • Clean Code
  • Conclusion
  • Points to remember
• 2. Clean Architecture Principles
  • Structure
  • Objective
  • The Application
  • The Domain layer
  • The Presentation layer
  • The UI layer
  • The Data layer
  • Navigation
  • Conclusion
  • Points to remember
• 3. Clean Architecture in Android
  • Structure
  • Objective
  • The Application
    • The Domain layer
    • The Presentation layer
  • The UI layer
    • The Data layer
  • Navigation
  • Conclusion
  • Points to remember
• 4. Unit Testing
  • Structure
  • Objective
    • The value of unit tests
    • Testing the Domain layer
    • Testing the Presentation layer
    • Testing the Data layer
    • The fallacy of test coverage
  • Conclusion
  • Points to remember
• 5. End-to-End Testing
  • Structure
  • Objective
  • The value of end-to-end tests
    • The robot pattern
    • Testing an Activity
    • Testing a fragment
    • Mocking the server
  • Conclusion
  • Points to remember
• 6. Failures and Exceptions
  • Structure
  • Objective
  • Failures or exceptions
  • Handling failures
  • Handling exceptions
  • Conclusion
  • Points to remember
• 7. Implementing a New Feature
  • Structure
  • Objective
  • The definition of a feature
    • Starting with the Domain layer
    • Implementing the Presentation layer
    • Implementing the UI layer
    • Implementing the Data and DataSource layers
    • Implementing navigation
    • Dealing with changes
  • Conclusion
  • Points to remember
• 8. Migrating An Existing Project
  • Structure
  • Objective
  • Existing Architectures
  • Gradual migration from MVP
  • Gradual migration from MVVM
  • Revisiting existing implementations
  • Conclusion
  • Points to remember
• 9. Other Bits and Bobs
  • Structure
  • Objective
  • Incidental and accidental duplication
  • Long-running operations
  • Sharing models across layers
  • Flattening and sanitizing data structures
  • Handling permissions
  • Cross-platform insights
  • Software engineering best practices
  • Conclusion
  • Points to remember
• Appendix: Project Setup
• Index