@hamen@VasiliyZukanov Basically yes, then you can also reuse them across projects or create a lib. For example, on my side, one thing I miss is WorkManager. I interface it with both iOS & Android implementations and it works well. Like Compose it will take a bit of times to be in truly amazing🚀
@hamen@VasiliyZukanov Not really an issue imho, you just use an interface so all calls & business logic are consistent and then you just write the implementation of each platform.
@JorgeCastilloPr Did you update the book with all the changes of the compose ecosystem over the years ? But maybe not that many changes regarding pure internals stuff
@joreilly In your last survey, I think Compose MP was the top answer. As KMP will be mainly used by Android devs; I'm not sure a lot of devs will bother with Swifui (even if it's super nice).
I guess it also depends on how much an app needs the iOS look and feel. But maybe I'm wrong😄
@tundsdev it's hard to find the right architecture with SwiftData. Everything is so tied to the UI. When you use @ ModelActor the update does not seem to work. I would love to see real-world architecture examples. Do you have some recommendations or resources🙏?
Currently diving into iOS development to master both Android and iOS. Coming from Android, I'm a bit surprised by how Apple has designed SwiftData🤔
Do any #iOSDevs out there have some recommendations for setting up a clean SwiftData architecture🙏? #swift#swiftlang#iosdev
When encountering SQL syntax issues in your .sq or .sqm files with SQLDelight, it's likely due to dialect mismatches.
You can resolve this by setting a dialect
#KMP#SQLDelight#AndroidDev
@HeyTolstoy So cool 🤩🤩
Now we need the ViewModel asap, even if there are some good alternatives made by the community.
Can also wait for Room, even if SQLDelight is powerful
Device Streaming in Android Studio is now in Open Alpha! This means you can access the service without registering for the Early Access Program - just download the latest version of Android Studio Jellyfish and link a Firebase project.
Device Streaming lets you test apps on real Android devices from a variety of OEMs located remotely in a Google data center, all through Android Studio. The service is free to use during the alpha period.
@Aivars_Meijers@SebastianRoehl For Android devs, Kotlin Multiplatform is a huge option to consider. You have a small learning curve and the performance of a native app. Even the UI part could be entirely shared with Compose multiplatform
Tip of the day:
Make use of Gradle typesafe accessors in your build scripts, if not already done.
You will get a nice auto-completion and compile-time checks for your modules.
#androiddev#gradle
@Nomns0 I would say compose phases and recompositions management.
Using compose is fairly easy but really understanding what is going on under the hood, how to debug and optimize it, especially in a pretty big app, can be challenging.
When we think a technology is game changer, comes a new one that shifts the entire landscape! Remember how RxJava revolutionized async programming?
Then Coroutines came, elevating the game with simpler and more efficient processes.
What would be the next big thing?#androiddev
@filippkowalski Have you considered Kotlin Multiplatform? You will be able to share all your business logic and also benefit from native performance. Also, as you already wrote the iOS app, you could even imagine later migrating your business logic and simply reusing your SwiftUI.