TurboMagic 92 Posted April 29, 2019 Hello, some question regarding Android splash screens. Delphi defines exact pixel sizes for these graphics. But where do they come from? Some colleague has written an app (in some web app framework) which uses completely different resolutions for those splash screens and if one tries to make similar looking one for my app this is quite cumbersome. These are the resolutions used by the other framework: 200x320 320x480 480x800 720*1280 960*1600 1280x1920 TurboMagic Share this post Link to post
Rollo62 536 Posted April 30, 2019 Maybe this may help you https://developer.android.com/guide/practices/screens_support.html#DesigningResources https://support.google.com/googleplay/android-developer/answer/1078870?hl=en&ref_topic=2897459 https://developer.android.com/training/multiscreen/screensizes I use the same image sizes as FMX bin\Artwork\Android provides, because thats approved and should be working. Share this post Link to post
TurboMagic 92 Posted May 1, 2019 Hello, thanks for the links provided. Some questions: You talk about approved image sizes and when I look at the path mentioned by you I see the resolutions the IDE project settings offer. But what does approved mean? Approved by whom? EMBT or Android or...? Or asked differently: why does a different development environment use different sizes? Who approved those? 😉 Isn't there some official standard as it is standard to have these ldpi, mdpi, hdpi etc. folders in the apk containing the various resolutions, but aren't those resolutions "fixed" somewhere? Share this post Link to post
Dalija Prasnikar 1396 Posted May 1, 2019 Android officially does not have splash screen support. Various frameworks only simulate splash screen while they load... so just use sizes Delphi asks and that should be it, The best is to use simple logo centered on black background (similar to default FMX splash). It is the least intrusive and will look good on various setups. If your application needs longer initialization, then make main FMX form as light as possible and then implement proper splash inside that can show progress and can be better customized. Share this post Link to post
Rollo62 536 Posted May 1, 2019 @TurboMagic Approved by Google and customers of the many Apps in the PlayStore using it 1:1. I wouldnt bother too much about the why' s. @Dalija Prasnikar +1 Use same strategy here too. I didnt found a reliable way to scale and fit real images in all screensizes. Would like to have that too, but its way too risky to get strange results in one of the 10000 devices out there. Share this post Link to post
TurboMagic 92 Posted May 2, 2019 On 5/1/2019 at 10:08 AM, Dalija Prasnikar said: Android officially does not have splash screen support. Various frameworks only simulate splash screen while they load... so just use sizes Delphi asks and that should be it, The best is to use simple logo centered on black background (similar to default FMX splash). It is the least intrusive and will look good on various setups. If your application needs longer initialization, then make main FMX form as light as possible and then implement proper splash inside that can show progress and can be better customized. The problem is, that it's not me who decides how the splash screen looks like. The other app is done in a different technology and uses different resolutions, so it's a bit hard for me to design a splash screen which looks similar enough from the logo and icon sizes of these elements on the splash screen. It would be a further argument for unification of development tools. Sigh! Share this post Link to post
Rollo62 536 Posted May 3, 2019 (edited) What about using a 9-patch images: http://docwiki.embarcadero.com/RADStudio/Rio/de/Verwenden_von_9-Patch-Grafiken_in_Android http://docwiki.embarcadero.com/RADStudio/Rio/de/Anwendungsoptionen https://stackoverflow.com/questions/13487124/android-splash-screen-sizes-for-ldpi-mdpi-hdpi-xhdpi-displays-eg-1024x76 https://github.com/yypbd/yypbd-Delphi-NinePatch https://medium.com/@101/splash-screen-in-android-769d3b0bafd0 But I think the basic problem stays the same, you won't get a pixel-perfect display on all devices (if that is needed). P.S.: I would consider if this is worth the efford for an image visible only once at startup. (but customers are kings ....) Edited May 3, 2019 by Rollo62 Share this post Link to post