A modern programming language that makes developers happier.

kotlinlang

Does anyone know any good open source examples or articles on how to best structure a compose application? or what patterns to use? i've tried using stuff from android but sometimes you just don't have libraries available to accomplish all of the same things

I learned a lot from this repo: <https://github.com/chrisbanes/tivi|https://github.com/chrisbanes/tivi>

I used KodeinDI as DI framework for our html and desktop apps. I made a simple ViewModel implementation to use cross platform as well. 

My production app Ashampoo Photos is based on this and I can generally recommend it:
<https://github.com/Kotlin/kmm-production-sample|https://github.com/Kotlin/kmm-production-sample>

This simple redux pattern is well suited to handle complex logic and make it testable.

I’ve found the <https://developer.android.com/topic/architecture|Android docs on Architecture> to be extremely helpful in thinking through my own projects and really understanding the why and how of mobile app architecture. And along with that, the <https://github.com/android/nowinandroid|Now in Android> is a pretty good implementation of the principles of those architecture documents

In particular, introducing an explicit <https://developer.android.com/topic/architecture/domain-layer|Domain Layer> has been the biggest improvement I’ve been making in my own projects lately. Using my <https://github.com/copper-leaf/ballast|Ballast MVI library> for the UI and an explicit Domain Layer has helped me to put logic in the right places to make even the most complex features pretty straightforward to implement.

My “stack” does introduce a fair amount of boilerplate, but what I get in return in terms of maintainability, testability, analytics, etc. is worth it for me.

<@UD17D4K8W> cool, that’s exactly what we did. It felt a bit over engineered at first. But when the app grows it really helps! DI was critical here though 

Yeah, I spent some time trying to get the arch to work with “manual DI”, but came to the conclusion that if the app is large enough to actually benefit from this “Clean Architecture” approach, it’s large enough that it needs proper DI. I’ve been using Koin and have been happy enough it it so far.

I’ve also been reading <https://www.georgefairbanks.com/e-book/|Just Enough Architecture>,  which has helped me understand _when_ to apply this “over-engineered” architecture (because it’s definitely overkill for smaller apps)