halcyonmobile / multiplatformplayground Goto Github PK

View Code? Open in Web Editor NEW

82.0 10.0 11.0 2.33 MB

Kotlin Multiplatform project in Jetpack Compose & SwiftUI with shared ViewModel layer and File upload

License: Apache License 2.0

Kotlin 83.79% Ruby 0.81% Swift 15.40%

kotlin-multiplatform viewmodel swiftui kotlin-native ktor kotlinx-coroutines backend usecase hierarchy android

multiplatformplayground's People

Contributors

Stargazers

Watchers

Forkers

f8full davidqphan alexgabor dariush-fathie ylpeng rajeshjadav fortunado rvenky125 nilsonsasaki bk-entrypoint kotlinfunc

multiplatformplayground's Issues

Fix collecting flows on the UI

We should revisit our flow collection logic on UI and make sure it follows:

https://medium.com/androiddevelopers/a-safer-way-to-collect-flows-from-android-uis-23080b1f8bda

Fix image upload on apple target

Image upload on apple targets is broken:

Works fine on Android
on iOS & macOS no logs, infinite loading

Try out the ios-suspendwrapper

https://github.com/FutureMind/kmm-ios-suspendwrapper

Implement category selection on upload

Try out the KMM version of detekt

detekt/detekt#3453 (review)

Fix ViewModel orientation-change issues

The current scoping & viewmodel providing should be replaced with injection by koin.

Create Desktop App

With JB Compose it should be relatively easy to migrate the current Android application to Desktop Apps.

Dependencies:

moko-resources needs to target JVM - #151

Steps:

Add jvm target to common
Add the needed actual jvm implementations
Create Desktop application based on current android app

Add a CI implementation

We should have the following stages:

Common (build & lint) -> than platform specific jobs (android, iOS, macOS, etc...)

Note:
The platform specific jobs shouldn't depend on each others, just on the common

Add `kotlin-multiplatform-mobile` topic

The Kotlin team is now changing its approach to the Multiplatform mobile samples. The number of great projects is growing, and we can't keep adding them to the already huge table in the documentation.

Instead, we decided to keep a handful of projects in the table and give a link to a handy search by the GitHub topic. To add the topic to your project, please use the kotlin-multiplatform-mobile tag in the About section of your GitHub repository.

Improve navigation UI/UX for top-level destinations

Currently BottomNavigationView is used to access the two main top-level destinations: Home and Favourites.

MaterialDesign guidelines recommend using it with at least 3 destinations, so maybe it would be a good idea to ditch the usage of bottom nav view and implement something more simple and usable. I.e: We could place the Favourites CTA on the Home screen's app bar and access it from there.

Document and setup GitHub action workflows

relates to #5

follow up on: https://kotlinlang.slack.com/archives/C3PQML5NU/p1610627305010700?thread_ts=1610551690.259400&cid=C3PQML5NU

This issue is exclusively about GitHub Actions. For other CI systems, please open other issues and link them back to #5

explore how Kotlin based project are setup
compare to a Java based project @MobilityData/gtfs-validator
add findings to this issue