-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
smooth transition from native splash sceen to an animated page - how to do? #692
Comments
@FetFrumos have you found a way to sync the static and dynamic images ? |
I thought we could discuss how we could contribute to this open source project, haha^^ |
Same! My client want a "fade in/out" animation |
This should be an easy one - at least a fade out on calling |
Well maybe not - have you checke the code in - https://github.com/jonbhanson/flutter_native_splash/blob/master/lib/flutter_native_splash.dart ? |
@BriceFab How did you eventually solve this problem? Thank you. |
@ziadsarour It's a little unclear where you got the FlutterNativeSplash.remove() line from. Is this a custom static method? |
if this stuff works should be part of the package |
|
I am working on a Flutter app for both Android and iOS, and I'm using the flutter_native_splash plugin to create a static splash screen. However, my client wants an animated splash screen immediately following the static one. The plugin doesn't support animations directly, so we agreed on a setup where a static splash screen is displayed first, followed by a custom animated splash screen built within Flutter.
The static splash screen is set up with flutter_native_splash, which scales the image to fit different device screens, but I'm unsure how to perfectly align the image size of the animated splash screen to match the static one.
What are the best practices to synchronize the image dimensions between the static image used by flutter_native_splash and the subsequent animated image in Flutter?
is this even possible? any advice - I will be very grateful
The text was updated successfully, but these errors were encountered: