Has anyone managed to get a smooth transition betw...

# compose-ios

[aidanvii]

Has anyone managed to get a smooth transition between a native iOS launch screen using plist approach and the compose view controller? I’m observing a white flash in between and looks quite jarring.

[Magnus Lundberg]

Is it the same issue as this?
https://kotlinlang.slack.com/archives/C0346LWVBJ4/p1692020102405959

[aidanvii]

I’m not sure, it could be

[aidanvii]

trying to find a workaround by obscuring the compose view controller with an extra SwiftUI splash screen until I receive a callback from the Kotlin side out to swift to notify that it’s “ready”

[aidanvii]

I’m not using iOS navigation, all in app navigation is handled by decompose

[aidanvii]

but it feels like it takes some time for the first frame to render, or something 🤔

[aidanvii]

looking at the video, it looks like it could be the same underlying issue

[Elijah Semyonov]

Yes, we are aware of that issue and currently working to resolve it. You could slap UIViewController constructed from LaunchScreen storyboard and fade it away in 100ms, should hide the issue for now.

[aidanvii]

that’s pretty much what I did actually 😅

[aidanvii]

so native iOS splashscreen from plist, to the compose view controller that’s obscured by a second SwiftUI splashscreen for a short time before fading

[Elijah Semyonov]

Right, should do the job, add a fancy dismiss animation on top, so it will be a sad experience to remove it once it’s not needed 🙂

[aidanvii]

for me it’s not a big deal as the app is 99% compose based, so I can get away with having a temporary SwiftUI splashscreen there without it looking too out of place. Navigation is all compose based (with decompose)

[aidanvii]

It’s fine I’ve gotten used to removing temporary workarounds for iOS, like dynamic light/dark theme and some other things 😄

[aidanvii]

or dialog support, I enjoyed deleting the code I wrote to do that, admittedly with a little tear in my eye 😅