Now you’re not really answering my point 
I think I have explained myself enough for someone to grasp where I am coming from. Equally, I think you and I are coming from two different backgrounds and are maybe not understanding each other very well.
I do understand it can be difficult to hear criticism, and fair enough if that is your stance then I wish you and the rest of the Wappler team all the very best. I will surely keep an eye on the releases.
yes, if you want to position Wappler to the designers (non technical users who don’t even know HTML yet but know UI/UX design)
If you wish to position Wappler for developers, that would be a different story, but a waste of potential IMO. Wappler has the potential to cater to a much larger audience.
also, FYI, when i started using Wappler, i did have basic HTML and CSS knowledge. but i had a tough time learning because of bootstrap (had never used it) also, honestly the documentation was not very clear to me - it felt bit jargon-y.
however, lucky for me, community helped a ton and so did @sid - else i’d given up long ago.
now, as long as am developing, Wappler will be my go to tool! 
That was the driving force for me to start the webinars, It allow me to show the technicalities while explaining the basics for those who need that extra input. I can spend a bit of time talking about things like bootstrap while demonstrating the how to’s of it all and of course people can ask questions as we go along.
@Teodor. You seem to use an absolute blanket response whenever someone talks about Wappler accommodating non-tech folk. From my personal perspective, I am not looking on 'how to design a web page from the very basics’. You made this comment to me previously when I clearly explained I knew html, css and js. In addition, I am an Art Director and have earned my stars in the design arena over countless years. These sort of comments come across as patronising and a real turn-off. I know my stuff, I am relatively intelligent and can grasp new concepts and deal with learning curves.
Edited to add. Some tech folk might also benefit from some ‘basic’ design skills too, of which there is a need judging on some of the gallery examples - sorry. Try explaining a Triadic colour wheel, or colour theory in general, negative space, the rule of thirds, kerning, ascenders, descenders and so on.
Note: @nshkrsh does have a point too, it wouldn’t hurt covering the basics for others.
If you want my subscription fees (and countless others), then it might be worth listening to the needs of us non-techy plebs, like myself. Surely you want my piece of the pie too?
I am also quite confused with whom your target audience is. You stated previously:
“We don’t expect every user to be a developer, but indeed we expect the users in our user base to have at least some basic knowledge of HTML, CSS and web site building”
Well I am that user! I have basic AND mid-level knowledge of web design. I can use parallax, write css grid for gods-sake, if that don’t make me at least basic then enlighten me. No, I don’t develo, but yes, I am looking for a no-code/low-code option, where I can grasp the ‘basics’ in a real-world / walkthrough situation. For the avoidance of doubt I have seen the recent webinar from Brian.
Carrying on with my confusion on who you are marketing to - Wappler web site also states:
“We asked ourselves one question: How do we accommodate designers of different experience levels? We answered this with an interface that adapts to the complexity of your designs. The seemingly simple interface is really just a pathway to much more advanced features that let you really dive into your creativity. Because we’ve focused on the beginner, design professional, and web developer, our visual tools are the most robust in the industry."
That simply isn’t the case. How can Wappler state “we’ve focused on the beginner” when your personal retort(s) state users need to know some basic knowledge of html, css and web site building?
Wappler should be taking up the gauntlet here, it’s the elephant in the room, a number of people have spoken about it on the forum and therefore there must also be a number of people who can’t be bothered or have looked at the offerings and thought ‘maybe later’. There’s a real chance here to increase your returns.
If you feel a ’basic’ level type bunch of video tutorials are too dumbed down - so what? They are for your customer base surely, not the internal Team.
I leave you with this - again from the Wappler site:
Afterall " Designers shouldn’t be limited by technology, they should be able to freely express their ideas and creative work. Without limitations, without borders. With the visual design tools Wappler offers, we think we achieved that goal. They look familiar as you would expect but with powers that lift all restrictions for just prototyping, giving you access to making fully functional, data driven, interactive websites and mobile apps. Gain coding powers, visually."
This would be great if the solution was really this elegant and wholly accurate.
Yes and thank you for doing this - Wappler should be paying you.
There were some gaps in there for me personally. Being selfish I want to know the benefits of using PHP, MYSQL etc. Why chose those options then others available within Wappler (unless I am mistaken)? You also missed some of the options on a pop-up window when connecting to the database - what they were for and why. I can’t remember what else but again, thank you for doing this. if you can get your screen sizing down pat and go real slow for us thicky-non-developers I will watch religiously.
I can answer the PHP MYSQL one easily, both are generally free so are universally available, Microsoft SQL is normally chargeable (and expensive) so not available to all
Bit confused on the database connection bit, I didn’t do a database connection, only a FTP connection. Database is the start of next week. But on FTP the only bit i recall missing (which I intended to mention) was Passive v Active FTP but in the real world passive tends to work with everything, Active is not always supported on shared platforms so stick with passive to be safe.
Agree with Pachamama here. Wappler team needs to find out which audience they want to cater to, because they seem a bit schizophrenic about that. They attract non-developers by virtue of having built this kind of software, but they usually don’t seem to like that, based on their reactions here on the forum.
They will help you though, they have done so in many cases, you just need to prod them a few times. I just hope they will become be a bit more customer centric, and (financially) encourage others like hyperbytes to create the content for them. Their business is now in a sense a leaky bucket in terms of customers coming in and leaving because of the lack of education. They should fix the leaky bucket first and then they will start converting more paid customers.
I agree to a level Nevil to some degree but, based on my own experiences the customer base is extremely diverse so it is very difficult to find a middle path. The “team” may one moment be asked something very technical then in the next post be asked something ridiculous like how would i write Amazon(dot)com with Wappler.
Very few questions remain unanswered and I do sympathise with the likes of Teodor who sees to have to give the same answer over and over again,. For example how may time has he had to tell someone to switch on Server Connect debugging to show the “real” error?
I think to some degree they are their own worst enemy in that they provide such a hands on one-to-one service that expectations remain much higher than you would normally expect from a software forum. How many other forums have direct input form the CEO?
But going back to the issue of basics, while my passion has always been IT I did, in a previous life, write law books and teach criminal law. I did not start my teaching with “this is a law book”, i had an anticipation that those wanting to learn would have perhaps covered the very basics. Same applies to basic concepts like Bootstrap, CSS, FTP, they are the equivalent to learning to put fuel in your car before a driving lesson.
I also think it is easier to criticise than be constructive, i hear lots of people saying things are too complicate but see few actually set out their precise requirements so they can be addressed. Sometimes the forum may be the answer, their are times a suitable link to an external source will be a better solution.
Either way, people need to take some responsibility for their own development, learners need to seek specific help, not expect to be blindly spoon fed until they finally get the flavour they want.
The forum is our friend but so is google, there is no benefit in re-inventing the wheel, bootstrap for example is covered extensively in other places, why try to reinvent the wheel? Is that a deficiency of the team or just laziness of the user? I will let you make up your own mind on that one.
And lastly, if things are missed in a post or a webinar, reply to the post or say something at the time in the webinar and i feel it is unfair to criticise about omissions which were not raised until after the event.
I fully agree with that, but just sometimes help is lacking here and the problem is: there is no where else to go. That is the frustrating part.
Also the team should remember: the fact that users like me, pachamama and others take all this time to create lengthy feedback is not because we don’t care, otherwise we would have left a long time ago. It’s (in my case at least) because we see the huge potential in this software and would like to learn a lot. Let’s call it passion 
not random criticism. And I will contribute something constructive when I have something to show for it
I do have some conflict with some of your comments:
“For example how may time has he had to tell someone to switch on Server Connect debugging to show the “real” error?”
I haven’t come up against this issue as I am not ready to subscribe. But I would also say if someone is repeating themselves - yes some people are lazy, some need spoon-feeding as you call it, others might simply not find the process intuitive. All three have to be solved with an elegant design solution - as frustrating as it may be.
“I had an anticipation that those wanting to learn would have perhaps covered the very basics. Same applies to basic concepts like Bootstrap, CSS, FTP, they are the equivalent to learning to put fuel in your car before a driving lesson. I also think it is easier to criticise than be constructive, I hear lots of people saying things are too complicate but see few actually set out their precise requirements so they can be addressed. Sometimes the forum may be the answer, their are times a suitable link to an external source will be a better solution.”
If you want to entice people into the Wappler infrastructure it would be best practice not to send them elsewhere to find the answer. That is lazy. Brand loyalty comes from anticipating the needs and furnishing the answers to their target audience. I feel like I am being taken to task for offering criticism. Criticism can and is constructive, and as hard to take, may offer insight too. Can you imagine how many times I have been told by someone, they don’t like something I have done, especially within the design field where a lot of the considerations are subjective?
“Either way, people need to take some responsibility for their own development, learners need to seek specific help, not expect to be blindly spoon fed until they finally get the flavour they want.”
Ummm, I think in this ‘instant fix’, ‘instant results’, highly competitive world we live in today, this won’t work. As valid as your point may (or may not) be, it is quite a sweeping assumption?
“The forum is our friend but so is Google, there is no benefit in re-inventing the wheel, bootstrap, for example, is covered extensively in other places, why try to reinvent the wheel? Is that a deficiency of the team or just laziness of the user? I will let you make up your own mind on that one.”
Totally ‘constructively’ disagree on this one. Just because something has been explained, done, rehashed elsewhere, does not mean it can’t be duplicated within the world of Wappler. I’ll let you make up your mind on that one, - maybe try to figure out why it could be incredibly important to do exactly the opposite of what you infer.
“And lastly, if things are missed in a post or a webinar, reply to the post or say something at the time in the webinar and i feel it is unfair to criticise about omissions which were not raised until after the event.”
I wish I could but I personally did not watch it live.
The way I feel comments have been made towards prospective customers (me) feels a bit like going to a comedy show and being heckled at the door before even getting through the entrance. I don;t feel especially woo-ed!
@nevil is correct on his last post and has reminded me how much effort and time I have spent on this forum - more time than any other! So good luck to you all, I wish Wappler the very best and will surely don the marble steps of Wappler with my lowly loafers if and when it fits my ethos.
I totally disagree with you @Teodor Webflow is like using Adobe Indesign, Illustratot, Photoshop and so on. I haven’t used Wappler yet but I’ve seen the videos tutorials (which are pretty boring) and all I can say is that Webflow UI is way much easier than Wappler.
I think the two are completely different tools. Webflow is more front-end and lots of fancy animations, styling, etc. Wappler is app development with powerful database features, etc. I think it could be an idea to use both as each specialises in its own area. You’re just not comparing eggs with eggs.
The best software so far for sure.