I just designed the interface. Then I pass to block code. But I realized that it is too slow. I get block in, Thunkable is being stopped for twenty second. It is exactly impossible to build an app. Please help. Why thunkable x block side are too slow to build block code?
I noticed this, too. I think it’s a trade-off between a desktop application which would be much faster and an online tool which is slower. It forces me to be more efficient in my coding. To ask myself: where can I combine blocks, use functions, etc. to make cleaner code?
The latest release of Thunkable X has an update that should dramatically improve blocks performance.
To ensure you are on the latest version, please hard refresh your browser.
It would be great if you could test with some of your larger projects and give us some feedback on your initial experience.
We did quite a bit of internal testing, but as you can image there are a huge number of possible block combinations so if you spot something - get in touch.
Also, if you like the update, feel free to let us know too!
I just tested it out! It seems to be working considerably bettter. I had quite a bit of lag at 1000 blocks. I now only see that lag during a test with 4000 blocks on 1 screen
I have a 899 blocks screen, and the speed has increased a lot, indeed! However I am experiencing the same issue @Daniel_Coglitore reported: when I alter anything on the blocks, navigator screen crashes. It is probably when thunkable tries to save. Also, when I try to live-test my app, it also crashes cause of some problem when trying to connect to Firebase through listening.
I believe these bugs are natural for a very recent version, and hope it could be easily solved. Congrats! Block dragging lag was really really annoying.
1200 blocks-I see a significant increase in the performance of the block editor. Blocks of global variables now do not cause freezing in the block editor as before, when in a large project, even one global variable block caused the block editor to freeze for a few seconds.
Unfortunately, it was not possible to increase the number of blocks to 4000, because after another copy of the function with 700 blocks, a white screen appeared in the block editor. I will see what this is related to.
I also run into this white screen issue a lot after the update… seems to be kind of the same problem users have with not being able to save their latest changes properly… only thing that helped so far is to wait a second or two after each block movement
Yes! have to avoid that crash , but I definitly rather to wait 5 segs after finishing changing all the blocks or moving aside a block I dont need to delete it later than wait 5 segs per move as It was before , very frustrating. without this lag thunkable feels totally different