Some good news for everyone on this Friday afterno...
# multiplatform
z
Some good news for everyone on this Friday afternoon: We have just shipped and announced a new default structure for KMP projects. kmp logo You can find all the details of the changes in the blog post or in

the video▾

.
TL;DR: No more
composeApp
, instead the new structure includes a
shared
module that serves as a KMP library and then separate app modules for every platform, such as
androidApp
,
desktopApp
, and so on. The new structure is already live in the wizard (both on kmp.new and in IDEs). You'll also find it in our docs and samples - the links to all those resources are also in the blog post. intellij idea Finally, alongside the new structure, AGP 9 support is for IntelliJ is finally available - thanks for your patience, everyone. Update to the latest 2026.1.2 release to get it!
kodee happy 13
🦜 6
K 24
🎉 28
c
image.png
b
Thats great, we are already doing that in our projects, keeping the platform specific modules super light. What we are finding is that we never work in them, so we'd would love to see them tucked into a sub directory. We mostly do that already, we stash them in <root>/apps/androidApp|desktopApp etc. (or <root>/platforms) the hard one is iosApp, it doesn't always play nice when we move it around. composeApp (your shared module) is the main entry point the platform uses, and everything else related to that.
@Chrys haha, I like the *App, its a quick visual indicator that you are in a special module 🙂
😄 1
a
We also tuck every application entry point inside the apps folder because they are rarely touched
👍 2
u
btw gradle convention is kebab case for modules
maybe 1
j
image.png
➕ 1
a
@zsmb Could you please clarify, how does the new module structure comply with need of Umbrella module in iOS ? Or it is not related, if we still include only `sharedUi`/
sharedLogic
into iOS? Are there any plans for separate modules export related to new modules structure? E.g. issues KT-42247 KT-42250
z
@Andrey Beryukhov There are no changes to the umbrella module situation with the new structure. Having an umbrella module is still the recommended way of integrating into an iOS app. • If you use shared UI, the
shared
module is the only KMP library module and is essentially the umbrella too. • If you use native UI, the same thing with
sharedLogic
instead as the module that's integrated into the iOS app being the umbrella.
thank you color 1
m
I prefer putting app modules inside an apps folder, it's much cleaner and makes them together instead of having an alphabet modules order so the android module will be on the top and web module at bottom for example. I hope this becomes the default even if server is not selected.
👍 1
j
I agree with Mohamed -> especially because now it is the rule, and not the exception, to have all the application targets in their own module. If you have android/web/jvm/ios targets, it would be clearer to put those in an app/ module to show: these are the launchable applications. Then you can either put the shared module next to it (because it kinda is the multiplatform part of all the applications and glues all other library modules and navigation stuff together), or at another level even (so you can distinguish between platform specific apps and shared libraries).
➕ 1
u
Sounds like package by layer..