Hi,
I noticed that there is a new feature to show a splash screen on latest daily build.
However, the image seems using as the same as default.png.
Will we be able to custom it for android devices?
Thanks,
Fu [import]uid: 4992 topic_id: 28824 reply_id: 328824[/import]
Android supports all of the “default.png” images that iOS does, including the @2 images, mentioned in the link below. The splash screen images will be “letterboxed” on Android.
http://developer.coronalabs.com/content/building-devices-iphoneipad#Launch_Image
We added iOS splash screen image support for convenience for simple apps. If you need any special splash screen resolutions then you would have to handle that yourself in your main.lua file. It’s quite easy. Just do a [lua]display.newImage()[/lua] in your main.lua file and then load all of your app’s resources via a [lua]timer.performWithDelay()[/lua] right afterwards. Larger apps tend to do it this way anyways. Especially to show progress on the splash screen for really huge apps.
Anyways, I hope this helps! [import]uid: 32256 topic_id: 28824 reply_id: 116270[/import]
Thank you.
Will we be able to only turn off Andriod splash screen support?
The dimenssions are different so that there are always black bars on top and bottom of the screen.
[import]uid: 4992 topic_id: 28824 reply_id: 116281[/import]
Unfortunately no. The only thing you can do is to remove the default.png files from your project directory and set up your own splash screen. Most apps do it this way anyways. There are so many different display resolutions between Android devices that it is really not worthing settings up custom default splash screen files for them all. Perhaps Nook and Kindle Fire might be worth doing, but what of the rest of the Android devices?
I suppose one other thing we could do is have the app look at the config.lua and check if it is set up for “zoomEven” and display the splash screen in the same manner… which of course means parts of your splash screen will be displayed off screen. [import]uid: 32256 topic_id: 28824 reply_id: 116746[/import]
Thanks for your answer.
I understand the hassle of porting splash image to all different Android devices.
Therefore my hope is only using default screen on iOS devices but not on Android devices.
Could Corona team add this option in the future update?
Thank you.
Fu [import]uid: 4992 topic_id: 28824 reply_id: 116802[/import]
Fu @fudesign, just in case this helps, the work-around I use is to keep another Default.png file for Android build. When I build for iOS, I use Default.png files specifically created for iOS, and when I build for Android, I replace them with a Default.png file specifically created for Android devices. It’s a bit of a hassle, but it does the job. (Since I swap sound and other art asset folders when I switch between iOS and Android, it just becomes part of the build procedure for me anyway.)
Naomi [import]uid: 67217 topic_id: 28824 reply_id: 116892[/import]
Hmm… perhaps an even better solution would be to have an option in the “build.settings” file that tells the build process which asset files to include/exclude. Something to resolve the asset file differences between platforms as Naomi mentioned. We’ll have to think about that a bit more.
In the meantime, doing what Naomi mentioned will work. Or you can display your own splash screen as I’ve mentioned up above. [import]uid: 32256 topic_id: 28824 reply_id: 116939[/import]
+1 for displaying the launch Default.png in the same manner as the app is displayed.
There’s no way to avoid the letterbox (which looks bad when it transitions to the full-screen app) other than omitting Default.png and having the user stare at a black screen for a few seconds.
[import]uid: 36578 topic_id: 28824 reply_id: 133484[/import]
Since the Default.png won’t match the resolution of the device, what do you propose we do? If we displayed the PNG in zoomEven, then content will get cut off which may look even worse. Again, the best solution is for you to handle this yourself. There’s simply too many different Android display sizes. [import]uid: 32256 topic_id: 28824 reply_id: 133594[/import]
I think it’s quite common to use a plain background with a logo occupying the center of the screen, or alternatively a textured or plain color background that matches the look of the app. Both of these will look fine cut off - they can be designed to spill over the edge.
I’ve tried handling this myself, and I can’t escape the 2 second black screen lag before the splash appears, even if I load the splash right at the beginning of the app, then launch my content on a timer.performWithDelay(1, launch).
[import]uid: 36578 topic_id: 28824 reply_id: 133624[/import]
+1 for displaying the launch Default.png in the same manner as the app is displayed.
There’s no way to avoid the letterbox (which looks bad when it transitions to the full-screen app) other than omitting Default.png and having the user stare at a black screen for a few seconds.
[import]uid: 36578 topic_id: 28824 reply_id: 133484[/import]
I think zoomEven is a bad idea. If content gets cut off, then your app may get rejected by app reviewers. Since screen sizes vary so wildly on Android, you’re more likely to run into this issue… and it is a common issue. For example, Barnes & Noble frequently rejects apps that exhibit this behavior.
As an alternative, you could set up your Default PNGs with black edges so that they blend nicely with the black letterbox area. I think that would be a better alternative. [import]uid: 32256 topic_id: 28824 reply_id: 133713[/import]
Since the Default.png won’t match the resolution of the device, what do you propose we do? If we displayed the PNG in zoomEven, then content will get cut off which may look even worse. Again, the best solution is for you to handle this yourself. There’s simply too many different Android display sizes. [import]uid: 32256 topic_id: 28824 reply_id: 133594[/import]
Letterbox is no better than zoomEven - it depends on the graphic being used. I think the best would be to allow the developer to choose which. [import]uid: 36578 topic_id: 28824 reply_id: 133801[/import]
I think it’s quite common to use a plain background with a logo occupying the center of the screen, or alternatively a textured or plain color background that matches the look of the app. Both of these will look fine cut off - they can be designed to spill over the edge.
I’ve tried handling this myself, and I can’t escape the 2 second black screen lag before the splash appears, even if I load the splash right at the beginning of the app, then launch my content on a timer.performWithDelay(1, launch).
[import]uid: 36578 topic_id: 28824 reply_id: 133624[/import]
I think zoomEven is a bad idea. If content gets cut off, then your app may get rejected by app reviewers. Since screen sizes vary so wildly on Android, you’re more likely to run into this issue… and it is a common issue. For example, Barnes & Noble frequently rejects apps that exhibit this behavior.
As an alternative, you could set up your Default PNGs with black edges so that they blend nicely with the black letterbox area. I think that would be a better alternative. [import]uid: 32256 topic_id: 28824 reply_id: 133713[/import]
Letterbox is no better than zoomEven - it depends on the graphic being used. I think the best would be to allow the developer to choose which. [import]uid: 36578 topic_id: 28824 reply_id: 133801[/import]