I hope you all understood correctly my comment about Thunkable being a no-code development tool (in specific situations like this).
For visual or simple workflows like said @jared, I’m absolutely sure that it is a no-code tool, but when we are dealing with complex projects, with many business rules, data loading, integrations with external APIs, it would certainly be very naive to assume that Thunkable would be codeless. This understanding I have since the day I started using the tool.
Anyway, I agree with you that even for the most complex things, the tool becomes “low coding”, as the use of the concept of blocks makes things much easier.
But the reason for my comment was that some situations go beyond knowing logic, math, or how to program; it’s not just about knowing what a block is for or how to organize the implementation. These are not so obvious things, because are related to functional characteristics of the product’s architecture that determine whether an implementation strategy/approach will work or not.
Unfortunately these situations are not exposed in the official tutorials or in the good documentation available, which forces us to learn in pain.
Things like that IMHO should be in advanced tutorials with implementation techniques, or provided in practical examples to avoid wasting time trying to find out the reason for these erratic behaviors while debugging the application. There are a lot of videos but most are just very basic stuff.
Looking through the questions here on the community forum, we found examples of questions like this one, which are only solved when someone who has been through the “pain” knows how to solve it and comes up with a recipe on how to do it. And luckily the community is very active and fast, but it’s time that could be saved if there were more advanced documentation.
I’m working on a single project, which is an ecosystem of multiple apps made with Thunkable, it’s been 7 months, time spent, partly because of my lack of experience with the tool, partly because of the complexity of the project and partly because I left coding in the last 25 years moving to IT management. Thats the reason I chose Thunkable
But fortunately I’m close to reaching the launch point. And because it’s a big project, the need for advanced resources is mandatory, and periodically I’m “stuck” in situations like this, and figuring out how NOT to do things, which delays the delivery, but I’m very grateful for the attention and help I receive from your side!