The changes made so far have been pushed to this branch of the Confetti repository.Along with our sister meetup group, GDG Berkeley, we are excited to have Siamak Ashrafi as our speaker for October 2020! Use an approach that allows having specific styling for each platform, something that can be done using Kotlin Multiplatform’s expect/actual mechanism. When sharing the same Compose code on on both platforms, we’d need to In this exploration I updated the colors, dimentions etc in the Compose code to match somewhat closely with what was used in the SwiftUI code. KMM-ViewModel library) and that also applies to the shared Compose code that we’re consuming here

TabView and navigation etc with just the inner content coming from shared Compose code in the 1st case.Īnother interesting aspect of this, in this particular project, is that the Compose and SwiftUI clients are sharing the same View Model (based on use of the Both versions here are using same SwiftUI based The following is what the Compose and SwiftUI based versions of that screen look like in the iOS application. NavigationLink ( destination : SessionDetailsView ( session : session ))

The SwiftUI code for the list of sessions includes, in both cases, the following code to navigate to the SessionDetailsView screen. Session and view more detailed information about it….and it’s that session details screen that we’re going to use as an example here. The current Android and iOS Confetti applications (as shown below) display a list of sessions for a particular conference. In this article I’m going to explore what would be involved in doing this for one of the screens Is the possibility of using Compose for iOS for some subset of the UI, either a particular screen or

My feeling is that the vast majority of iOS UI development will be done using SwiftUI butĪn interesting area that a number of folks have written about (for example this article by Touchlab) In the PeopleInSpace sample I also created, some time ago, a separate basic standalone Compose for iOSĬlient as an initial exploration of the technology. Most of the Kotlin Mutliplatform samples I’ve created have focussed on the sharing of non-UI code and have included a fully SwiftUI based iOS client,Īlong primarily with Compose clients for the other platforms (e.g.

Kotlin compose ios