Some aspects of the architecture will only be useful in large, complex applications. In smaller, simpler projects they might become boring boilerplate that you can do without. You are, in fact, encouraged to cut a few corners here and there, and take just the parts of the architecture that you need.
Here are some ways you might be able to simplify your application.
The architecture prescribes a lot of mapping by default, between at least three layers of different model objects. While this is for good reason, as explained in that theory section, it’s also a lot of code to write if your models in the different layers are very similar to each other.
There might also be performance reasons for wishing to reduce mapping, but this tends to be quite rare. Mapping happens on a background thread anyway.
There are two recommended ways of reducing the mapping work necessary:
Using domain models as presentation models.
You may propagate your domain models to the UI if they’re of the appropriate structure, and you find them easy enough to display as they are. These models should be pure Kotlin classes, so this doesn’t leak any library details to the presentation layer. All you’re losing is the screen-specific formatting of these models.
If you find that there are some screens where you do need to reformat or restructure your models for presentation, you can always introduce presentation models for just that specific screen, lazily.
Using data source models as domain models.
This should usually be the disk data source’s model, as the database tends to be source of truth for an application, and the database model’s structure is less likely to change than that of the network models.
When there’s little formatting to perform before displaying your data, or your application has very little client side business logic, it might not make sense to build out all the layers described in the architecture. You might end up with methods in each layer just calling into the corresponding method in the next layer, and doing nothing else.
There is a recommended shortcut to take, but feel free to come up with your own as well.
Merging presenters and interactors. This will bring two major changes in responsibilities and structure. It will make moving to the background thread the Interactor’s duty, so all of the methods in its public interface should now start with a
withIOContext call. The other change is that these Interactors, unlike Presenters, can be shared between different ViewModels.