They should depend only view and repositories interfaces, so this three elements can be moved together to common-client. In MVP, all business logic should be placed in presenters or use-cases. General idea in context of multiplatform Kotlin development is also described here. If you are not familiar with it then check out this presentation or some of the articles about it. This is why I think it is the best candidate for multiplatform Kotlin project with shared clients logic. It is also one of the most important ideas behind MVP architecture. Although it is one of most important postulate of Clean Architecture.

There are a lot of different development architectures, but most of them are not making parts where business logic is implemented independently from platform. If you refresh project now, you will have two additional modules configured. Generally expected class declaration is a definition of class and its methods that needs to be implemented in every platform module (currently only common-jvm).Īs long as we are not using any methods on common module, we can replace Date declaration with DateTime defined as follow in common: Better approach is to implement for such classes expected declaration in common module, and actual declarations in common-jvm. Although we would then have to change in whole project how we use them. Simple workaround is to hide such declarations behind interfaces or replace them with primitives (like Long with millis in this case). Such classes will throw error because common modules cannot use platform specific features. Often example is when they use Calendar or Date from Java standard library. If your data model don’t depend on any platform dependent classes then you don’t need to add anything to common-jvm and everything will work fine.īigger problem is when some classes moved to common module depended on platform specific classes or libraries. As long as packages didn’t change, everything else should work well in your project.

To move them, we only need to move files from android source to common module source. They should not be platform dependent so they can be easily moved to common module. Both of them should not include any logic, but only properties and functions that are used to hold and get representation of data. Often there are also DTO objects which represents how API sees data. Extract data modelĭata model is a set of classes that represents how we see data in our application. When you sync your project, you should have all set up.

What is android studio module