https://kotlinlang.org logo
Join Slack
Powered by
using compose ui for multiplatform the ios app siz...
# compose-ios
s
using compose ui for multiplatform the ios app size is increasing very high. for a simple hello world app with compose ui it is taking arround 32mb where writing with swift it is taking only 108kb. why this is happening and how can we reduce this
r
Yes. Do you have a question?
s
the reason for this
r
Your Swift app relies mostly on APIs that are part of the OS. Your Kotlin app does not and packs things like Skiko
I think you can try disabling bitcode
🆗 1
s
it is out side the scope of the question but in current situation if i want to build a ui library that that targets both ios and android (i want to publish the library to maven and cocoapods) which is better compose multiplatform or flutter
r
You're asking on Kotlin Slack, of course the answer will be Compose
Ask a Flutter community and they'll say Flutter
😅 3
j
Impossible to compare Flutter vs Compose. But I think blueprint in Flutter is even worse, but could be wrong. I would say avoid building ui libraries multiplatform at current state, but if have to I would say Compose is most possible easier to maintain over time compared to Flutter from my experience.
h
Flutter also (still?) uses skia, so this dependency will increase your bundle too
j
Also 32MB isnt that much imo, and you can also reduce it by using proguard and such minify the blueprint 🙂
s
my prob statement is the library should be less in size and have basic functionalities like api call, load images and videos
the people who will use my library in their ios app should not increase the app Size Significantly
j
Whats the reason need UI layer btw? Just wonder if possible to use maybe only Kotlin multiplatform without the compose layer.
s
how can i get the .app file from android studio. after build the file is getting deleted i guess
116 Views
Open in Slack
PreviousNext
Powered by