Been doing jetpack compose and kotlin made a basic...

# compose

[Pranav Kataria]

Been doing jetpack compose and kotlin made a basic app on which when you tap on an image the image and the text changes and the second image requires a random number of taps bw 2 to 4 so when i made the project initially made a single composable function which contained how the ui would look and i coded the logic inside it only but as i made the project i ended up using two composable functions
Which defined how the ui would look
For updating the ui states or how the ui elements would behave
I wanted to ask is this approach correct like is my thinking as to how to develop an app just by an idea or a ui basically i wanted to know how a senior developer approaches it the map of the app in their mind the steps etc

[Stylianos Gakis]

Don't post the same question in two channels
https://kotlinlang.slack.com/archives/C04TPPEQKEJ/p1720122168526659?thread_ts=1720122168.526659&cid=C04TPPEQKEJ

[Max]

@Pranav Kataria I suggest checking out some medium sized example projects on Github (e.g. from @Philipp Lackner ‘s YT channel), and get familiar with the project setup. And then you remodel those best practices.

I personally approach starting a new project by having a rough outline in my mind, creating a base project structure with feature modules for each feature, just showing the title of the feature on the screen. Then i connect it together so i can navigate between them. The you have a sceleton you can iterate on. That’s for the ui

Core wise i prefer setting up di, networking directly by investing some time instead of “quick quick and the iterating”, bc the fundament of the app is a pain to refactor, so there is spent the time it needs to be production ready from the get go

[Pranav Kataria]

@Max thanks a lot this is very insightful !!