Hello everyone, havent done pure Native Android de...

# android

[Nikola Milovic]

Hello everyone, havent done pure Native Android development in a while, last time I did, ViewModel fragments were the go to, alongside Repository/ UseCase pattern. Everything would be split into either Feature modules or Data/Domain/Presentation. (Everything i mentioned is of course opinionated, but this did provide quite a nice layout for the project)

Now my question is what is todays goto clean architecture, tech stack considering Compose is staple for UI, are there any new libraries that make development easier? Any sample projects/ examples and your opinions are highly appreciated.

[Max Ferrier]

Hi !
One of the best repo about Android good practices is the TiVi application (Compose, Flow, Coroutines, MVI, etc.). But it's a bit hard to start with that if you haven't done pure Android since a while ^^
I could suggest you first projects from skydoves (especially this one)

[Nikola Drljaca]

I wouldn't say Compose UI is staple yet, there still a lot of ground to cover. As far as the tech stack goes, ViewModels/Fragments are still the way to go, but depending on the navigation library you choose you may or may not use fragments. Everything else you mentioned can most certainly be the way to go.
Also, the projects Max linked are a good starting point I think.

[Max Ferrier]

Yep, Fragment could be avoid now. In the TiVi projet, you have a state Flow of data loaded in the ViewModel directly observed in the screen.
Also, if you need a project with xml layouts and the "classic" fragment/VM pattern, you can find this project on the Android GitHub repo