Hi, I don’t know how many of you have noticed this, but on using start value when switching screen, in my case from screen1 to screen2. It lags for a while and definitely it’s slower than switching screen without start value.
Btw, I am using correct method to switch screens.
convert into apk,then use .in companion it lags bcz of internet latency
I have tested in apk, seems like the issue is same in both block (with and without start value)
Screen switching is slow in kodular, from screen1 to screen2
can u try without use close screen block
I have tried that too
would you like to show your full block code
I am sure my blocks are correct, I have been using kodular for so long, you may try yourself.
when we switch from screen2 to screen3 there’s no lag, but this screen1 to screen2 lags
add a spinning notifier and dismiss it just before switching on screen1, you will notice that the spinning notifier disappears but the screen1 lags for a while before switching
I created an empty apk and tried the same thing, it’s fast. So the problem might be the number of blocks I have in screen2 which is around 1800.
I faced it before, this issue sometimes cause app not to respond in expected time
For me
I can recommend Tinydb onclick save your values then open screen, on Screen.Initialize call TinyDB1.GetValue
Sometimes it works
Did you try opening that screen without a start value block? If not it’s the open start value
Just a suggestion 
even without start value, it lags..
this is the recommended method to switch screens, read this
The issue lies in the kodular
You are switching screen in a method which is taking some time to complete and then moves to new screen.
You need to show the blocks which are there before changing the screen.
Try to remove all procedures from row created method and just try to open new screen.
