'Jetpack Compose structure
I have a question
Now, for example, in the old days, we had different activities, we had different fragments The code was divided into different files
For example, each of the 200 lines of code could be easily worked with The ui code was completely separate in xml There were logical codes in the fragment, and eventually things went in separate classes
Now with compose and mvvm How does this happen? How can the codes be divided? Does the concept of fragmentation and activity still make sense? In those architectures, we meant the high level of activity and fragment code What can be replaced in compose?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|
