CatViewerDemo - GitLite

KO | EN

gitlite — search

#python #hacktoberfest #react #llm #android #rust #nodejs #windows #awesome #cli #vue #awesome-list #mcp #openai

CatViewerDemo

(★ 106)

Kotlin Multiplatform Mobile demo for Android and iOS. App for viewing Cat pictures

파일 탐색기

최종 버전 다운로드 (.zip)

- - push.yml
- ci-gradle.properties
- .gitignore
- build.gradle.kts
- - google-services.json
  - GoogleService-Info.plist
- - gradle-wrapper.jar
  - gradle-wrapper.properties
- libs.versions.toml
- - AppDelegate.swift
  - ContentView.swift
  - Info.plist
  - iOSApp.swift
- - project.pbxproj
- - Info.plist
  - iosAppTests.swift
- - Info.plist
  - iosAppUITests.swift
- .gitignore
- android_demo.gif
- ios_demo.gif
- build.gradle.kts
.gitignore
build.gradle.kts
gradle.properties
gradlew
gradlew.bat
LICENSE
README.md
settings.gradle.kts

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/MartinRajniak/CatViewerDemo

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd CatViewerDemo

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Gradle (Java/Kotlin)

보통 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
JDK (Java) Java/Kotlin 프로젝트를 빌드/실행하려면 필요합니다.
Gradle 레포에 포함된 gradlew(Gradle Wrapper)를 쓰면 Gradle을 따로 설치할 필요가 없습니다.

cd androidApp

이 프로젝트의 관련 파일이 하위 폴더 안에 있어서, 먼저 그 폴더로 이동합니다.

./gradlew build

Gradle로 빌드를 진행합니다.

✅ BUILD SUCCESSFUL 메시지가 뜨면 성공입니다. build/ 폴더에 결과물이 생성됩니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# CatViewerDemo
![Check](https://github.com/MartinRajniak/CatViewerDemo/actions/workflows/push.yml/badge.svg)

Android demo                                                          |  iOS demo
:--------------------------------------------------------------------:|:-------------------------------------------------------------:
<img src="readme/android_demo.gif" alt="Android Demo" width="300" />  |  <img src="readme/ios_demo.gif" alt="iOS Demo" width="300" />

Kotlin Multiplatform Mobile demo for Android and iOS. 
App for viewing Cat pictures from [Cats API](https://thecatapi.com).

This sample showcases:
* [Kotlin Multiplatform Mobile](https://kotlinlang.org/docs/kmm-overview.html)
* [Android Architecture](https://developer.android.com/jetpack/guide)
* Shared state management with [Flow](https://kotlinlang.org/docs/flow.html)
* Networking with [Ktor](https://ktor.io)
* Persisting state with [Multiplatform Settings](https://github.com/russhwolf/multiplatform-settings)
* Logging with [Kermit](https://github.com/touchlab/Kermit)
* Android UI with [Jetpack Compose](https://developer.android.com/jetpack/compose)
* iOS UI with [SwiftUI](https://developer.apple.com/xcode/swiftui/)
* Android image (GIF) loading with [Coil](https://coil-kt.github.io/coil/)
* UI tests
* Unit tests

## Usage
I leave here some notes that might help anyone who would like to build it themselves.

### Cats API key
The project is using a property named `catsApiKey` to retrieve the key for the API.

You can provide it through `gradle.properties`, for example.

### Kotlin Multiplatform Mobile setup
You should follow [KMM setup](https://kotlinlang.org/docs/kmm-setup.html) 
to build the application, both for Android and iOS.

### Google Services 
Google Services configuration file is required for Crashlytics, which the app uses to report issues to the authors.
If you want to build and run the app, you need to create your own Firebase project:

1. Create a project on [Firebase console](https://console.firebase.google.com/).
2. Add applications using the package name `eu.rajniak.cat.android` for Android and `eu.rajniak.cat.iosApp` for iOS.
3. Follow the instructions and download the configuration file to the appropriate folder.
   Refer to [setup Android](https://firebase.google.com/docs/android/setup) or [setup iOS](https://firebase.google.com/docs/ios/setup) for further details.
4. Enable Crashlytics on the Firebase console.

In case you don't want to create a new Firebase project,
you can still build applications with [dummy configuration files](config/dummy).
Keep in mind that applications with this config will not run.

This guide is inspired by [code-with-the-italians/bundel](https://github.com/code-with-the-italians/bundel/blob/main/CONTRIBUTING.md).

### Dependency updates
To keep dependencies updated [Version Catalog Update Plugin](https://github.com/littlerobots/version-catalog-update-plugin) is used.

All you need to do is to run `./gradlew versionCatalogUpdate`.

## Overview
The goal of the exercise was to build Kotlin Multiplatform Mobile applications for Android and iOS,
with only UI written in platform-specific code (ComposeUI and SwiftUI).

Everything from ViewModel to Repository and data sources is shared.

## Architecture
Architecture follows the standard blueprint proposed in
[Guide to app architecture](https://developer.android.com/jetpack/guide).

### Shared module
The shared module consists of Kotlin Multiplatform code that I use to share business and presentation logic
between Android and iOS.

#### ViewModel
<b>CatsViewModel</b> is the class that UI platform-specific code interacts with.
It prepares cats data displayed in the UI. It also listens to the actions that happen in UI.

It extends <b>SharedViewModel</b> that provides shared scope for coroutine work.
I took inspiration from [MOKO MVVM library](https://github.com/icerockdev/moko-mvvm),
which I plan to use instead once there is more time.

#### Repository
<b>CatsStore</b> is responsible for providing Cats model data.
It fetches data from <b>CatsApi</b> and <SettingsStorage> to map it 
to model data used in application.

In the future, I might use the Mapper pattern for mapping data from external systems to domain models.

Data from <b>CatsApi</b> is intentionally not persisted,
to provide up-to-date results.

#### CatsApi
<b>CatsApi</b> uses Ktor to fetch data from [Cats API](https://thecatapi.com).

#### SettingsStorage
<b>SettingsStorage</b> provides platform specific implementations for key value storage.
On Android it is [Datastore](https://developer.android.com/topic/libraries/architecture/datastore).

#### CatViewerServiceLocator
All dependencies are provided by <b>CatViewerServiceLocator</b>.
For such a small application, it perfectly serves its purpose.

For larger applications, I would recommend 
[Hilt (DI library)](https://developer.android.com/training/dependency-injection/hilt-android).

### Android platform-specific UI

<b>MainActivity</b> is a single activity in the application
as the only application entry point. Even with more screens,
I would still recommend using single activity
as screens can be represented as composable functions now.

<b>CatsUI</b> file
and composable function currently represent the only screen in the application.
I divided the file into multiple functions for clarity.

### iOS platform specific UI

<b>CatsView</b> is single screen displaying list of Cats.
Cats are represented by <b>CatItem</b> view. For filtering,
<CatsFilter> view has been created and is displayed as a sheet.

<b>CatsStore</b> serves as adapter between Kotlin Flow world and SwiftUI.

### Tests
Shared code has one test file with a bunch of basic unit tests.
You can find them in <b>CatsTest</b>.

I test the shared code through the ViewModel interface and
I use Fakes for external systems like networking and IO.

It allows us to test most of the business logic from a single interface.
Once I add more logic to tested objects, I might need to write more isolated tests.

There is also one UI instrumentation test in the Android application module. 
It runs with dummy ComponentActivity provided by the test library.
It allows us to test the UI in isolation.

## Special thanks
This project was way simpler thanks to all the resources,
libraries and projects I was able to find on this topic.

### CatsAPI
First and foremost, thanks to the people that created and maintained
a free public service API that I could use to showcase KMM.

### John O'Reilly
His [repositories](https://github.com/joreilly) that showcase Kotlin Multiplatform were crucial to my work.

Especially, [repository](https://github.com/joreilly/MortyComposeKMM) that demonstrates paging.
I could not use the same multiplatform paging library (time constraints),
but I  want to try it in the future.

### Touchlab
People at [Touchlab](https://touchlab.co) and all the resources they provide publicly
were especially helpful for my understanding of how Kotlin native threading works.

### Jetbrains and community
During the project, I was using Apple M1 Silicon and with it arm64 simulators. 
Support in libraries is getting better, but the community on #kotlin-lang Slack channel,
was extremely helpful when I was fighting with this.

### Others
Special thanks also to all people that share their solutions around Kotlin Multiplatform.
It is hard to find any up-to-date resources, so every single one of them counts.

Thanks to all the Kotlin Multiplatform libraries out there.
I used:
- [Multiplatform Settings](https://github.com/russhwolf/multiplatform-settings)
- [Kermit](https://github.com/touchlab/Kermit)
- [Kotlin Multiplatform UUID](https://github.com/benasher44/uuid/)
- [BuildKonfig](https://github.com/yshrsmz/BuildKonfig)

## TODO
Some things were left undone.

### GIFs
[Coil](https://coil-kt.github.io/coil/) on Android helps us with displaying GIFs,
but this has not yet been implemented on iOS.

### Caching
[Coil](https://coil-kt.github.io/coil/) on Android is already caching images on disk,
but there is no caching of images on iOS.

### Error Handling
There is almost no error handling implemented at the moment.

It would be nice to show errors when image loading fails,
there is a network issue, etc.

### Full-screen view
It would be nice to be able to display images on full screen.

I could showcase [Navigation with Compose](https://developer.android.com/jetpack/compose/navigation),
since I would have another screen.

### Continuous Integration
I believe that even when developing a project alone,
Continuous Integration service can help.

I would at least know that the build, tests and static analysis run with every new commit.

Another advantage is that I can be sure that someone else (another machine) can build it.

GitHub should be able to provide this functionality.

### UI improvements
There is a lot of work on UI.

One thing that stands out is filtering,
I don't think it is intuitive at this point.
But it is there primarily to show work with Flows,
so it is OK for now.

### Bugs
There are probably a lot of bugs, but one stands out.

Pagination, loading of new images is working nicely.
But only when the user scrolls to the bottom of the list.

But new images are not loaded when the user gets to the bottom
by filtering.