Maybe in the future we will be able to learn best practices of development within Wappler itself, by studying professionally prepared projects.
I usually get some kickback when I make these comments. But none is necessary. I represent a small segment of people who bought Wappler to ease themselves into new app technologies and have been very frustrated with things that I search to undertstand & so often have to scour the internet outside of Wappler docs and then try to come back into Wappler to see if my understanding is applicable in Wappler.
When I started out learning html, php, mysql queries & connections to save & display data and rudimentary javascript nothing helped more to learn the principles than Working Examples. Modifying functions by trial and error to see the effects, researching other code examples and bringing them into a project to see how they worked and how I could modify them for my needs. Same with jquery, different flavors of javascript.
Wappler Top-Down brain trust consistently resists this – insisting that Visual Approach Wappler UI is more than sufficient to complete every step to the end.
In fact, making a Tutorial project’s completed code exposed for learning is pooh-poohed.
Unlike with open-source front and back end stacks.
The 100% Visual Approach does not teach the proprietary logic BEHIND so many Wappler methodologies. Which is why the Forum over the years is filled with “why this, why that?” after the fail occurs. Then long threads trying to get to the bottom of the confusion.
The dependence on proprietary App Connect for everything to work, is, of course, an understandable PRO & Con decision that does make Wappler a very useful tool.
But the Learning Curve & inconsistent applicability of Docs to This Version of Wappler has been a hassle for this geezer 
.
My learning curve is massively accelerated by being able to trace and analyze a complete efficient, Professionally developed Learning Demo application PARTICULARLY in the Mobile App arena and Desktop app platforms.
