Mkhytar Mkhoian

Software Engineer. Co-organizer of Silicon Drinkabout Kyiv

[Mkhytar Mkhoian @mkhytar]

@RysychPavel It doesn't matter. The product and how fast you can build, and iterate, this is what matter

[Mkhytar Mkhoian @mkhytar]

@Lupin_Ai_Coder AI

[Hamdan le maudit @Maxcorleone667]

@RBR_Daily Checo is a legend

[Mkhytar Mkhoian @mkhytar]

It's good practice to execute different types of tasks on different dispatchers (or thread pools). for IO operation better to use https://t.co/9NSJvd05AM. Pass dispatcher through class constructor to make testing easier.
#androiddev

[Mkhytar Mkhoian @mkhytar]

You should not allow direct access to the data layer from the UI layer, everything goes through the domain layer. An advantage of making this restriction is that it stops your UI from bypassing domain layer logic.

#androiddev #android

[Mkhytar Mkhoian @mkhytar]

#androiddev

[Mkhytar Mkhoian @mkhytar]

The logic for mapping the Domain models into Presentation and vice versa should be in the Presentation layer. Models in this layer can be platform-dependent (e.g. Parcelable) and be more UI-specific.
#androiddev #architecture #domain #presentation

[Mkhytar Mkhoian @mkhytar]

The model on this layer shouldn’t be Parcalable or any other platform-dependent code. This layer is the source of truth in the project and should be platform-independent, so we can reuse it for different platforms (e.g. Kotlin multiplatform project).
#androiddev

[Mkhytar Mkhoian @mkhytar]

You shouldn’t expose source-related exceptions to the app, rather map it to the exception that your app knows how to work with.
#androiddev

[droidCon @droidcon]

Add #Deeplinks to support to your #Android #app 📲 By @mkhytar

https://t.co/w2sLcHkltg

[Mkhytar Mkhoian @mkhytar]

Avoid names based on an implementation detail — for example, UserSQLiteDataSource—because repositories that use that data source shouldn't know how the data is saved. Following this rule will allow you to change the implementation of the data source.
#androiddev

[Mkhytar Mkhoian @mkhytar]

Some unit tests should be avoided because of their low value. The golden rule is not to cover a framework or library components and interactions with them that do not contain business logic.
#androiddev #tests

[Mkhytar Mkhoian @mkhytar]

Often we need fake data for testing and the nice way to organize fake data is to use the ObjectMother pattern. It’s useful to have a nice library to generate fake data for tests. It’s useful when you’re developing a new project and need some pretty data for showcase.
#androiddev

[Mkhytar Mkhoian @mkhytar]

The separate data models give us the flexibility to customize it to fit the transport protocol. It provides better separation of concerns, for example, members of a team could work individually on the different layers of a feature if the model class is defined beforehand.

[Mkhytar Mkhoian @mkhytar]

I want to emphasize on that the Domain layer should be the most stable in your app architecture. That means independent from other layers and platform-independent code which makes it safer to make changes without causing unexpected problems.

#androiddev #architecture

[Mkhytar Mkhoian @mkhytar]

My advice is to follow the Dependency Inversion Principle (DIP). The domain layer should communicate with the data layer only via the interface, for example, repository or service. Those interfaces must be placed in the domain layer and implemented in the data layer.

#androiddev

[Mkhytar Mkhoian @mkhytar]

The main idea of the use case is to be a simple and lightweight piece of business logic and only have responsibility over a single functionality to follow the single responsibility principle.

#androiddev #architecture #solid #usecase

[Mkhytar Mkhoian @mkhytar]

#androiddev #architecture #domainlayer

[droidCon @droidcon]

Testing your #app is an integral part of the #AppDevelopment process – go over #JUnitTests 🧪 By @mkhytar #AndroidDev

https://t.co/MHiG5Gbghc

[Mkhytar Mkhoian @mkhytar]

#androiddev #architecture #kotlin