Sorry, I don’t agree with that at all. While there probably are a number of people using Wappler who could be considered as non-coders, I doubt it’s anywhere near the majority. Non-coders will generally steer towards Wordpress, page builders, plugins, etc. to achieve what they want and won’t give Wappler any consideration.
Let me rephrase that then: people that don’t know what binary search is.
Anyway, I can already infer from the popularity of the FR that not many people agree with me. That’s OK.
Still I believe in my analysis of the situation and if I am wrong I won’t mind backtracking.
I have strong opinions loosely held.
Definitely you have to know quite a lot of “code” to use Wappler. So many technologies are employed, interwoven via thousands of lines of code governing CSS, framework interpolations, server connections, functions, classes, flows, browser engines, etc. to just make a dynamic project that queries, filters, writes and retrieves data from databases.
Wappler for all of its modules & grooviness is still not a “non-coder” tool.
But then this is due to the complexity Web 2023 demands for everything beyond a static page.
It is amazing what these genius founders have accomplished to this day!
The builder app is only available to you while you are subscribed. This builder produces code that belongs to you, but for that code to be useful it is using some frameworks and libraries that don’t belong to you.
Those frameworks and libraries are owned by Wappler and are copyrighted therefore you can’t use them or modify them without their permission.
The permission to use them(not modify them) is granted in their terms.
You are allowed to continue using the App Connect and Server Connect frameworks on your web sites and mobile apps even after your subscription expires and you don’t have a valid Wappler license any longer. You will just not be able to get any new components and security updates.
So worst case scenario your app will continue working as-is.
The builder will eventually fail to run for one of these two reasons depending on what worst case scenario we are talking about.
- Your subscription ends and you can’t renew
- The builder can’t validate your license against their license server.
Once that happens you would be able to modify your code with other tools (vscode, notepad, vim), but only YOUR code. Not the libraries that are copyrighted so you wouldn’t be able to patch or improve Server Connect or App Connect from a legal perspective.
At that point in time you should already be looking at rebuilding your app as it wouldn’t be wise for any business to be messing around with copyright infringements.
Not just IDE and IDK tools are threatened by AI but Developers’ uniqueness.
I follow quite a few AI projects daily and the new Open Source Large Language Models released into the wild for installation on home computers.
Absolutely the direction is this: Talk, describe what you want your app to do, then answer the questions AI requires to refine your application vision.
Ai will be able to create entire projects, offer multiple UI stylings, search features, API connections. AI will even create custom API’s and integrate them into the app where needed, fitting the precise specs.
AI will also have comprehensive knowledge of stacks on servers so that it can match the components for best performance in each environment. AI will tell you what is necessary to scale up for rising demands. Hosting companies, clouds will employ AI to match your account & the apps running for optimization on the fly.
AI will detect flaws in software upgrades done by a human team and will disable the flaws or write a workaround or improve the upgrade by debugging it and installing the software it has fixed.
More and more hosting techies will be sitting around cafes as AI takes over server maintenance duties. AI will much more quickly be able to combat a Denial of Service Attack or respond to hacks. AI will be very adept at preventing security breaches because it will know every possible avenue of malevolent attacks and be able to INTELLIGENTLY monitor outside sniffing and even whip up a custom honey pot to foil hackers.
But beyond this some AI projects are already quite advanced in having their AI models innovate to the extent of writing entirely new machine code and programming languages that are not dependent on human engineered code that is running our machines now. And AI has also been turned loose on designing the hardware processors, the chips themselves.
AI is going to give us new types of processors to run AI engineered programming languages on these processors. The processors and machine code will be optimized by AI & it will write the software that most efficiently extracts all of the power of the whole hardware system.
The Wappler of the future will be astonishingly capable of executing anything you can imagine. And, really, truly, AI projects have made astonishing leaps that you will be hearing about over this summer, Fall, Winter. AI sophistication is learning, developing at a blistering pace.
Or it is powered by VC funds.
has anyone tried noodl? is it any good/easy to use/develop on?
There is a learning curve. You need to rewire a bit your brain to work with a UI that is adapted to designing for composable architecture. I used it for a bit a few months ago to test it out. But since my company transferred me to a team that was working on a Svelte project I finally decided to pour the hours into Svelte, Sveltekit, Tailwind, etc. At the rate AI tooling is advancing in VS code(copilot) the entry barrier for regular coding is plummeting.
Noodl is a great alternative to Wappler. I would say right now it’s the only good alternative out there. Their UI now seems a bit dated against Wappler’s one due to the latest changes in version 6.
But their commitment to open source makes up for it as they have been pouting engineering time there instead of the UI. They also generate react code for the frontend so if you need to extend the platform you have a huge ecosystem to work with.
For the cloud backend they provide their custom one based on the Parse platform but they are working on detaching the Noodle app from it as part of the Open source transition. So I guess in the end you will end up with a SPA based on react and you will choose a backend for it. Being that one based on the current parse integration which will make things easier or by BYO backend. I believe they have a community integration for Supabase.
What I don’t like is their design system. They need to improve that and add support for tailwind.
Noodl just dropped a bomb on their discord.
Instead of going “open core” (mix of free open source and paywalled features geared to commercial/pro/enterprise users) they are going 100% open source releasing everything they got.
For most this means that they will have a 100% free low-code platform to develop apps and deploy wherever they want backed by a core team coming from the parent company and the community.
Myself, I am more interested in following the transition journey from commercial to open-source as there are not many successful examples out there to learn from. I think it is quite interesting.