How does Kodular maintain screens, really?

[Taifun]

@Edvard_Drake

Item 1 and 2 implies very clearly to me that the Initialize should NOT be run when when returning to a screen after another screen closes

correct
therefore you will have to test the switching of screens (as it originally was intented by MIT App Inventor using the manager screen method) in an apk file as the companion does have these limitations

alternatively store everything in TinyDB and follow this advice

How to switch screens correctly

I see many issues done by users because they switched screens not correct. This below is now just one of many other solutions: [blocks] If you dont open/close screens correct your app will get possible runtime errors. Possible errors: (example) Unable to add window -- token android.os.BinderProxy@45d459c0 is not valid; is your activity running? Iam sure you don’t want that. Then please do it in the future and switch screens correct. General Tips and Tricks for App Inventor/Makeroid …

see also tip 1 here

General Tips and Tricks for App Inventor/Kodular

Use different screens wisely Before starting to create another screen, first you should think about is it really necessary? See also Building apps with many screens and SteveJG’s post about advantages/disadvantages, because in only one screen you also can use vertical arrangements to simulate different screens, just set the arrangements to visible = true/false as needed… If you decided to use different screens, then you should switch them correctly, else you will run out of memory after a wh…

Taifun