I am not 100% sure about the scope of the Splash Screen Control Plugin. Is the following correct?
a current license is required when building an update to an existing app for that app to remain splash free
it relates purely to building and there is no conditional runtime or any other form of service check for a license
Yes, if you update an existing app, you will need a the Splash Screen Plugin to keep that app splash screen free.
It is a build time check. If you release an app today, using the splash screen plugin, then a year from now you choose to not renew the plugin, your apps in the wild will stay splash screen free. But if you do an update after your license expires, any one running the update will get a splash screen.
Rob
Okay, thanks. I have to say that the reality of a $300 p.a. subscription cost for normal, splash-free app with Admob is in direct opposition to your marketing. I wish marketeers wouldn’t stretch reality so.
Yes, if you update an existing app, you will need a the Splash Screen Plugin to keep that app splash screen free.
It is a build time check. If you release an app today, using the splash screen plugin, then a year from now you choose to not renew the plugin, your apps in the wild will stay splash screen free. But if you do an update after your license expires, any one running the update will get a splash screen.
Rob
Okay, thanks. I have to say that the reality of a $300 p.a. subscription cost for normal, splash-free app with Admob is in direct opposition to your marketing. I wish marketeers wouldn’t stretch reality so.