Android

Having automatic verifications is an important part of Software Development, as the project and team grows it becomes crucial that no regressions are introduced into the "main" branch by mistake.

In Kotlin Multiplatform, writing platform-specific implementations is sometimes necessary. However, these implementations can introduce inconsistencies between platforms if not properly tested and verified. In this article, we will explore how to tackle this problem.

Data Builders provide an easy way for creating GraphQL response classes. In this post I'll show how they can be used to improve your tests.

Databases are an integral part of mobile application development, so it's important that these features are properly tested.

Recently I reactivated my old project Timi which I used to learn Compose. This time my focus is on learning the iOS side of Kotlin Multiplatform, I'm hoping that this experience will help me better understand my colleagues on the other platform. Working on a smaller project also allows for

Writing UI tests for pager layouts can be problematic in Compose. In this post, I'll share my experience and solutions when dealing with such screens.

MockEngine replaces real network calls with mocked ones that use pre-defined data and status codes. The engine can be shared between Integration and UI tests.

This article shows an example modularization strategy for Kotlin Multiplatform Mobile projects and touches on some issues related to modularization and the iOS platform.

This part focuses on the Android app of the Kotlin Multiplatform project