Got it, thanks.
How about the case of Android??
When I set:
splashScreen = { enable = false },
NO plash image shown, dark screen until the launch of the first app menu, although I have all the Defaultxxx.png included.
When I set:
splashScreen = { enable = true, image = “Default-Landscape.png”},
this “Default-Landscape.png” will be scaled to display as splash image. However, there will be a short period of dark screen afterwards, before the launch of the first app menu.
Hi Simon,
A1) I haven’t seen the submissions you sent to Charles yet, but I assume they’re tasteful and already meet most (perhaps all) of the guidelines we listed in the more formalized contest announcement. I doubt you submitted an entry with a green Corona logo on a pink background. 
That being said, if you want to tweak your submissions and re-submit, you can, but we’ll also review what you already submitted and let you know if we need more updated versions.
A2) There will be more details coming on this in the near future. My advice is to just take a deep breath and not speculate on things needlessly. Again, there will be clarification coming. In the meantime, as Rob mentioned in an earlier post, we’re all pushing forward, heads down and keyboards clicking, working on things to make Corona even better.
Brent
What about corona cloud? The announcement of a corona based cloud was a minor reason for me to stick with corona. Now, when I have to pay for the plugin, it is a even more interesting question for me.
@wilsonwansun, Native android does not even support launch images. Many years ago our Android developers wanted a splash screen, so in an attempt to make it cross-platform and with iOS only using two different images, we had Corona look and show those images, but that code got old and didn’t keep up with Apple’s UILaunchImage system. As part of this, we now let you control the splash screen with the plugin with build.settings. You can now design something that looks good and not depend on the Default.png.
Based on what I know( I don’t work for corona), corona cloud is not being worked on. Chris is out doing other things.
Edit: there are other solutions available.
Because have not found daily build #2953 at https://developer.coronalabs.com/downloads/daily-builds/ , I upgraded #2954 to resolve that problem. " Powered by Corona Labs" splash became invisible but i also can’t setting my splash image when boot game.Splash screen look like not shown or disabled.
Please confirm this bug and fix quickly as soon as able. I cant’t update new version for my game until this bug be resolved! Really troubling!
https://forums.coronalabs.com/topic/65637-corona-enterprise-20162949-android-splash-screen-bug/
Apparently, this new “feature” has created a NEW issue. We can no longer use a single code-base in build.settings for multiple platforms. Yes, after paying your $99, you will no longer be able to create multi-platform builds without first changing code in build.settings every time.
The only way around this is to handle the Default Splash Screen in the same manner for every platform.
To read more about this, I’ve created a new Topic at: https://forums.coronalabs.com/topic/65687-default-splash-screen-no-more-single-codebase-for-multiple-platforms/
@troylyndon
Agree with you.
@Rob Miracle
If I need to show launch screen as image on Android and as Storyboard on iOS do I need to edit build.settings?
[lua]settings = {
– splashScreen = { enable = false }, – for iOS
splashScreen = { enable = true, image = “Default-Landscape.png”}, – for Android[/lua]
I think would be better to have an FAQ blog post to answer some questions, especially when it will be implemented and also pricing per account, etc…
I don’t have time to do native on 2 platforms (or rather, my clients won’t pay so much for native), so cross platform is the only way my company is staying afloat.
It is ok for Corona’s USD99/year charge. It is optional and those that dont want to pay can continue using it for free. I was kinda shocked and worried when Corona became free a while back, but with this charge, i am more assured that Corona can stay.
Those are all addressed actually. It’s already implemented with the current daily builds starting from 2949 and costs $99 / year per account except Enterprise subscription. Here: https://coronalabs.com/blog/2016/09/19/corona-major-build-release-2016-2949/
@mynet, I’ll see what I can find about using the splash screen plugin with Enterprise builds.
@troylyndon, see my response on your other thread. Any one else? It’s here: https://forums.coronalabs.com/topic/65687-default-splash-screen-no-more-single-codebase-for-multiple-platforms/
I have a quick question. BTW, I think it’s a fair price (as a Corona Pro subscriber before).
If I remove the splash screen, will my existing default.png files still work? Or will I need to use the “custom” feature of the plugin?
I have a lot of apps and I don’t want to go “experimenting” (as the documentation says) with splash screen sizes again. Cordova uses a set image size and does the resizing for you (1024 for icon and 2208x2208 for splash screen – which it resizes). That would be ideal.
I really don’t mind paying, but since the splash screen doesn’t show in the simulator (does it?), I could have released this to the markets without being informed. I only “happened” to be looking at the Corona page to find it.
On iOS, the existing Launch Image techniques (Default*.png +UILaunchImages in build.settings or the Storyboard variant) still works. Our splash screen (or yours if you are using the splash screen controls) shows second. Apple does not require launch images. If you’re only building for iOS, disabling our screen and continuing to use the existing Apple launch image system will work.
On Android, the operating system has never supported launch images. We had built in a splash screen feature way back when that read Apple’s Default.png and Default@2x.png but nothing else. This splash screen control replaces that antiquated method we were doing. If you’re targeting Android, we no longer look at Default.png and Default@2x.png. If you are building for both, perhaps not using UILaunchImages at all and just depending on the splash screen we use would be best.
A square to 4:3 image in the 2000 pixel range is perfect for this. We will resize it and images always look better resized down than up. I think we set a size of 2048 on the long size for the splash screen contest. It should look good on a black background.
@mynet and Enterprise developers. If you want to use the splash screen with Enterprise builds (not simulator builds):
For iOS, place an image named _CoronaSplashScreen.png in the root of the app bundle. Make sure to specify it as a resource in Xcode.
For Android, put the image_corona_splash_screen.png in the res/drawable folder using whatever technique works for you in Android Studio or via the file system.
Rob
-
I have no problem with Corona adding the splash screen to help promote the brand but my issue is the loading screen looks scarey, too big and not attractive and that can put people off, especially those who are used to seeing your custom logo and all of a sudden they see corona. They might think your app had been hacked :(. Trust me there are some users who are careful of changes to apps or games.
-
Also adding as part of my update log “New loading screen from corona” so at least they know its from me looks funny.
-
What percentage of Corona users are real developers and what percentage are Reskinners? As I am still learning Corona, most of my games are bought templates from market places and this new splash screen just does not help us.
-
I use Buildbox and you could imagine the cost of subscription but if you see their logo, you would prefer it to your own logo
. If only Corona had a simple GUI like buildbox, life would have been amazing…
So in conclusion, most people here are not happy not because of promoting your brand but simply YOU DID NOT CARRY YOUR USERS ALONG HENCE MAKING THEM FEEL THAT THEY ARE NOT VALUED…
Whatever the case is, I am still sticking to Corona because of 2 people " Rob & Charles")
Now, For iOS, i don’t need more setting to splash screen is working normally.
But Android, “put the image_corona_splash_screen.png in the res/drawable folder” is not good. That’s troubling. i think.
I want to setting splash screen both Android and iOS like on old version of corona enterprise.(setting Default-568h@2x.png, Default.png, Default@2x.png at root of game project.)
But when update latest version of enterprise, i can’t configuring splash by that way. So disappointed 
Could you confirm this for me, please. Developing business apps.
a) I pay the $99 and disable the splash.
b) Finish project and hand off the code to the client.
c) Client uses code and on the anniversary of my paying the $99, the splash reappears (unless I have paid another $99)
or
c) Client uses another developer for updates/enhancements - splash reappears (unless they have paid their $99)
I personally have no problem with the $99. I DO want to be able to disclose application behavior changes in the development contract.
This may be a case for the option to pay per app as a 1 time shutoff or annually for app apps of a developer.
Hi @davida. This is a great question. Basically the check to see if an app should show a Corona splash screen happens at build time. If you have an active subscription to the plugin at the time of the build and deploy that app to a store, any one who downloads that build should not get a splash screen regardless of the current state of the subscription. If you do an update to an app after the subscription to the splash screen plugin lapses, then that build will start showing a splash screen. If you re-up the subscription and do a new build, the splash screen should go away.
If you give your code to your client and they build and deploy to the store, then, your customer would need to buy the plugin and they would have to keep renewing it if they want to continue updates without a splash screen. Whom ever hits the build button needs an active subscription.
Rob