Kodular getting slower

[rodrigosemfio (Rodrigo A. L. de Oliveira)]

Many screens are bad, but to avoid screens you need a large designer on the same screen, so the companion starts to show anomalies, also needs more blocks, which slows everything down.
This is true of all the AppInventor tools I have used. Use AppInventor from before you can create new screens.
That’s why I proposed these things:

Create tabs on blocks, folders on assets and multi display

Friends App Inventor based platforms are really wonderful, they allow us to build apps without worrying about the boring stuff of APP development. But as the project grows, some things get in the way of the workflow. I will present three solutions that would help a lot. 1 - Possibility to create folders in assets to organize and find more quickly what we want. 2 - Create tabs in the blocks, allowing us to separate our programming, making life much easier. 3 - Possibility to use multi displa…

Honestly, I do not understand how the first two proposals do not exist. Is it just me who suffers from it?

[Boban (Boban Stojmenovic)]

with more than 1500 blocks it’s almost impossible to move anything, it takes around 2 to 3 seconds to start dragging a block or pan the work area

Damn, that much lag on 1500 blocks

Then I should not recommend trying this one, as I had 5-6 seconds delay on it

Erro compilation in my project

Bill_Hamburgueria_teste.aia (6.9 MB)

Screen Screen1.bky contains 41 blocks
Screen Screen2.bky contains 136 blocks
Screen Screen3.bky contains 141 blocks
Screen Screen4.bky contains 13821 blocks
The AIA project Bill_Hamburgueria_teste.aia contains 14139 blocks spread across 4 screens.

[Robert (Robert Crum)]

Regardless of the BIG MISTAKE of having more than 10 screens (No app needs more than ten screens, and I challenge anyone to prove me wrong

Next daily challenge: Show an app, wich needs at least 11 screens to work efficiently.

[Taifun]

wich needs at least 11 screens to work efficiently

you might want to read again this Building Apps with Many Screens
Taifun

[gchcreaciones (German Caraballo)]

As soon as I have the finished project if it allows me to kodulate it, I will show it to you and the challenge will be the other way around, I will challenge you to see if this app is so wide, you are able to do it in less than 10 screens

[gchcreaciones (German Caraballo)]

Well it seems that closing all the blocks of the whole application lets me work. I hope to finish the project because restructuring everything now would almost start over. For next projects I will consider more these details that tell me. Thanks to all for the help

[Italo]

Ok, I’m waiting to see your app and tell you that you don’t need that many screens.

[Italo]

Don’t forget we are still waiting to see your app.

[sonumohammad333 (Sonu Mohammad)]

I am suggesting @Kodular
These tips may become solution in future
1.Kodular needs to build its own block editor instead of “Blockly editor”
2.Kodular needs to build a software for PC like Android Studio (Kodular Creator/Kodular Studio). With Inbuilt emulator for testing. So there will be no performance issues with browser. (Saves projects in PC/Cloud). Compile app in PC itself.
3.Kodular needs to build a platform like Stadia (by Google)
Stadia is a gaming platform where Stadia performs all gaming activity on Stadia servers (without users hardware) and streams to user in browser. But this method is only useful if user has high speed network connection.

[deanart2012 (Dean Artis)]

Sounds great but who will pay for it all? People are already complaining about the “high” commissions for ads but those only go towards keeping Kodular up and running.