still new to kmp. I used the wizard to generate th...
# multiplatform
c
still new to kmp. I used the wizard to generate the project. but I'm confused where there isn't an androidApp module. shouldn't there be?
only iOSApp module/dir. i would have thought an android module should also be created
p
In theory no, you don't need an extra module just to consume Android or JS or JVM. Is a simpler setup. Only one gradle module with all the platforms in it. The examples before were multiple modules. One that shared code for the different platforms and one module per consuming platform. I think jetbrains decided to go with this simple approach to attract newcomers. Once they know how gradle modules work they will move to multimodule approach for scalability reasons. Same as every medium to big Android project out there.
c
interesting. i wonder if i should just do that now. In my head it makes sense to have β€’ androidApp β€’ iOSApp β€’ composeApp as top level dirs
p
I prefer that structure too because it is more oriented to write platform specific code. But jetbrains seems to go for simplicity to attract new players.
πŸ‘ 1
It seems that many people complained about a basic Hello World setup having too many directories.
πŸ‘ 1
c
cool. okay. as long as it was expected.
i couldn't find an activity at first and i thought the wizard was broken
πŸ‘ 1
πŸ˜… 1
πŸ˜„ 1
a
had exactly the same issue at first but ended up liking 1 module instead of multiple
πŸŽ‰ 1
🐐 1
πŸ‘ 2
c
The goat is here
😁 1
❀️ 1
p
The future looks moving into that direction, only one module. As compose multiplatform ecosystem matures the need to write platform independent code will tend to zero.
πŸ‘€ 1
βž• 1