Conclusion: Clean Architecture Benefits

We have seen the following principles:

– MVC is not a suitable architecture for a Unity app.


– Testing is only possible with a well defined and loosely coupled architecture.


– How good architecture makes changes easy to implement.


– Clean Unity architecture principles, VIP cycle, and data independence. 


– How to break down use cases into business, presentation, and display logic.


– How software architecture and the underlying design patterns (Factory,

Observer etc.) can help you to conceive reusable a reusable codebase.

Some small reminder on Clean Unity’s VIP cycle:
 


– The view controller handles MonoBehaviours object lifecycle or accepts a user event, constructs a Request Data Transfer Object then sends it to the interactor.

– The interactor implements some logic work with the request, constructs a Response DTO object then sends it to the presenter. 


– The presenter formats the data in the response, and then apply the formatted data to the scene objects.

You can find the full source code and unit tests on https://github.com/Clean- Unity/CleanAchiever.
Well done ! You have finished this handbook, and now you can start applying Clean Architecture principles to your Unity projects !