In that case what I had done I’ll tell you when screen initialize show image and activate clock timer, when clock timer, get data from database, hide image and clock timer false
Soham, in the video you can see that to get to the splash image, it has a white screen of about 15 seconds, sometimes much more. Only after that time does the image and timer start.
please, would there be another way to do this? As I understand it, what I did was exactly what you suggested.
What happens when you remove the clock timer block from screen initialize and instead in screen initialize just set an image visible to true and also please show all the designer properties of Screen1
I did as you suggested but the time is still too high. I removed the timer and put a button for when it is clicked opens another feature.
@ledumelo
I believe this can help you:
Async Procedures Extension
and for the long time taken for your app to run, you have to debug your blocks and see if any for loops is doing a heavy work and I suggest testing on another phone.
I already have done some testing on this issue, after creating this topic
And we might consider the possible causes are device versions also… I found out that it just took 3-4 seconds for android 9 with enough RAM, so also some assets size trigger also. Try to install your app in the latest android device.
Silver, I just call it an arrangement that I call a splash in the initialize. I don’t use a timer or a counter for that. However, other arrangements that are not called and are hidden have slightly slower procedures. Even if these procuredures are not called, can they impact the initial application load?
I tried on 3 different cell phones and all the initial charge time is very long.
Are those device support Android 9 or? Mine android 8 take so long also. But in some cases you might consider the device version also…
I need the application to run on android 6 or higher.
No, if it is not called it won’t impact the initial application loading.
@ledumelo
Can you list everything you have tried so far to solve this problem?
you can also follow this guide:
https://community.kodular.io/t/long-delay-on-app-start-solved/69102
1 Like
-
I removed all the arrangements that were starting with a timer. Now there is only one that is visible and has a button in the middle to trigger the rest of the processes.
-
I removed the package name
-
I have few images in the asset and all do not exceed 40kb added. I don’t use any image directly, I call the image only when I use it.
I don’t know how to use logcat so I know which block is overloading the process.
I have a data dictionary that I load at the beginning. Can this type of variable affect the load time?
disable those two blocks and test your app…
It did not decrease anything to disable the blocks.
you have to now, so we can get a better understanding of this issue so we can help you 
I will try to install and understand how logcat works.
1 Like
this will help you now and for future 
1 Like