What is Default Splash Screen?

Solar2D General Questions/Discussion
#381

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.

#382

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/

#383

@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/

#384

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.  

#385

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.

#386

@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

#387

  • 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 :slight_smile: . 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")

#388

@Rob 

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  :frowning:

#389

@rob

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.

#390

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

#391

Thanks, @Rob.

That’s the way it should work.

Dave

#392

Here is a +1 for the splash screen.  I don’t mind it and probably nobody will either. I can always show mine after the initial splash screen. For me at least it is not worth the $99.00 bucks to remove it. 

#393

“Don’t piss down my back and tell me it’s raining” - Josey Wales

This quote appears to be the sentiment of many.

Taking a feature that was available previously and suddenly charging for the same feature, without advance notice, seems to be the primary complaint. A fair complaint to be sure. However the minimal price is not an issue in my situation given that I appreciate all that Corona allows me to do, especially if bugs that impact every single Corona developer, like this:

https://forums.coronalabs.com/topic/62256-tableview-error-question/

Can be dispatched more promptly.

---- Corona, this is the question I have:

Before purchasing this plugin I have a question though: Does Corona intend to convert other “features” we currently enjoy “free of charge” into “non-free” plugins in say, the next 3, 6 or 12 months? I would think that if this is the case that discussions around this issue should be well under way internally and it would be decent to give us a heads up to where this is going. As someone who has started, run, and sold 2 businesses, I understand the need for a revenue stream (preferably multiple streams) and will gladly contribute to said stream for use of this great tool. With that in mind, everyone from the largest business to solo home hobbyist needs cost certainty to be able to plan 3, 6 or 12 months out. That sounds reasonable, doesn’t it?

—STOP READING HERE IF YOU DON’T WANT TO READ HOW I THINK THIS SHOULD BE HANDLED—

  1. Extend!! Corona should offer non-free plugins that extend existing functionality to create truly “premium” functionality above what we already have. This would be easy to achieve  by simply going through the feature requests and go the premium plugin route for popular functionality they add, as well as making libraries such as the Widget library much more robust (and premium) for people like myself who develop business apps.

  2. Differentiate!! Don’t just add a splash screen because “everyone else does it”. Lua is crazy simple to learn so build on that advantage. Is anyone else working on a world class framework for building business apps? The ability to build useful business apps that have more power to access hardware would be nice without having to Frankenstein an app via an Enterprise account. A robust bluetooth or widget premium plugin could be a nice start.

  3. Communicate!! I know, nerds are often snarly introverts who don’t want to look up from their keyboards much less explain what we are doing, but sharing a roadmap can go a long way in building good will. Make us partners in where this is going and we will gladly follow, dump surprises on us and foment a rebellion. Human nature being what it is, it is easy to give something (such as making Pro free - probably a mistake) but very hard to take something away (we had splash screens before, now suddenly we don’t). A little less “fog of war” could go a long way!

I get tired of reading a single, long post so I’ll stop here as I could go on an on with ideas but I hope someone from Corona reads and can at least answer the question I have posted above.

Thank you for reading!

Ed

#394

+1 - I agree with Ed here.

#395

I wonder how this is going to work where my currently splash screen transitions right into an animation right after (eye blink).  Even if I do purchase the plugin.

https://youtu.be/0-Yr4uceadA

Is Corona gonna jump right in the middle of that?

#396

I have the problem the corona splash screen is shown just a half second, and after that I have a black screen for a half second. Is that a known issue?

#397

I think we can improve the quality of corona by add a monthly gift to a user for the better post, free plugin… And the gift will be a free version of the corona enterprise for one year

#398

@funkyvisions the flow goes:

iOS:  UILaunchImange -> Corona Splash Screen -> Anything you do in main.lua + other modules.

Android: Corona Splash Screen -> Anything you do in main.lua + other modules.

@sunmils, in theory the splash screen should stay up for around two seconds, but if the OS is slow loading/starting the app, it could impact that duration. So as to not hijack this thread, why don’t you open a new thread around the timing of the splash screen

#399

Thats true, I will open a new thread with a sample video.

#400

Crap. That’s definitely going to affect my flow. No more blinking eye for me I guess.