Screen Confusion... Which one to use and why

[Still-learning (1-2-3-4...)]

@Anthony007

EVERYTHING, AGAIN

If you do with procedure then you will less pressure

[Anthony007 (Tony)]

yes, the app is coming out to around 30 screens and each screen calls another screens, so EVERYTHING AGAIN!

[Anthony007 (Tony)]

Dora, you will be proud of me…

[Still-learning (1-2-3-4...)]

@Anthony007

around 30 screens

May be you will feel trouble after compiling app or during compiling or while opening the app. Sorry to say this.

(PS:If nothing happened as i said above then you are lucky)

[Taifun]

@Anthony007

the app is coming out to around 30 screens

you might want to follow tip 1

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

[Anthony007 (Tony)]

Thanks for that.

Unfortunatly I didnt begin that way som stuck with what I have…

[Anthony007 (Tony)]

Can you imagine using one screen to handle the equivalent of 30 screens. Finding stuff will be an absolute nightmare… unless you have vays undt means, ja?

[Anthony007 (Tony)]

but provided one closes and opens every screen properly I can see no reason for any “memory” problems.

That is of course if the Kodular method of closing a screen has been well coded as to flush not simply close a screen