Structuring Android Applications Around Domain-Driven Design
A small Android application can usually survive with screens, ViewModels, repositories, and a few API classes. Once the product becomes more complicated, however, technical layers alone may no longer describe what the software actually does. Imagine a marketplace app containing payments, inventory, shipping, customer accounts, promotions, subscriptions, and order management. All of these areas use data, but they follow very different business rules. This is where structuring Android applications around Domain-Driven Design can become useful. Domain-Driven Design, commonly called DDD, ...
