You have basically already done this with wapplerâŚrefactor the program into a database like the video program Davinci resolve⌠we should not have to create a database when we create the app or the web page⌠because the project is the DATABASE. I am now adjusting to the logic which is basically php but it is still tediuosâŚ10 times easier then trying to learn each function and nuance. And I am no php expert⌠but I am learning the flow of php with wappler⌠in essense you have create a database or encylopedia of php /asp code snippets that I do not have to remember or really even know how it worksâŚ(how visual programming should be) but I am repeating myself a lot with the logic and flow. You are doing a great job⌠and this is just a feature Request⌠you are doing nothing wrong. You guys are great. And the support is great! 
and I am recommending Wappler to everyone I know.
What I just suggested has not even been created(livecode almost has thisâŚthey are just are missing the database piece which I am a trying to build with livecode). I do not have time to sit around and write code for the web and server side. That is why I bought wappler. Wappler team has effectively programmed all the server side syntax in php and asp to programmable snippets that we can create serverside apps a remarkable feat. Itâs just a widget that does this in the background so I can save myself a few extra stepsâŚkeep all the others and cheers to your freedomâŚmore time is all I seek.
Actually we have this planned as a Database Creator in Wappler. So you will be able to create database structures and meta data directly in Wappler!
This will be also very useful for the mobile app or when client side database are required because those databases need to be created on the fly for each user.
That said - the Database Creator is indeed a large undertaking so we will do it once we implemented all the base components, so it has a bit lower priority right now
Any updates on a database creator?
I personally donât think I would use it. I just donât see it being able to do it as easily and efficiently as Navicat. I could be wrong though.
Also very interested in the database creator!
We will be working on it this summer. It is a complex matter but very needed not only when using hosting but also for local databases when building apps.
So we want to get it right and weâll in Wappler visual way style.
Something licke âkickstartingâ a DB would be nice. I mean to be honest, mostly we have for user DBâs each time the same columns like ID, name, lastname, birthday, city, etc etc.
Also for products some stuff are similar. But maybe it could be done more âgenericâ like speaking of objects instead of products or articles. And maybe at the end some âcustomizationâ could help, where a user just could change rows etc. What about to have some kickstart snippets from community driven library? So all these projects which are done on wappler could be shared in SOME parts.
So somebody could just put his âaddressbook kickstart dbâ into that wappler community (
Star Rated) asset folder?
Here my old link for Snippet Library. So that feature could be merged together and increase community shared snippets a lot!
@George I read somewhere that you were planning to include version control for DBs.
How are you planning to approach this? Through migrations? Or something else?
Well initially we will be making database creation and management as easy as possible in Wappler.
This means that you will be able to manage an existing database structures but also create new ones.
Basic features and usage
For people without much database experience we will even be supplying a built-in database services in the form of SQLite. So you can easily create a simple database and just use it without the hassle of running a full blown database server. (read bubble users 
)
Also we will be offering âmetaâ database management, so that you not only enter your table/fields info - but also their purpose and validation. So you will have simple types like text, file, image, etc and you can focus on what to store than how.
This way we will be able to auto-generate all the needed Server Connect CRUD actions, with validation but also file upload, validation etc when needed. Also we will be able to generate much richer client side forms with the file upload and validation as well - because we have all this meta data.
Advanced features
For the advanced users we will be binding all this with git version control. You will be adding support for version numbering and do indeed automatic migrations between versions. We are looking to empower the same migration methodology as sequelize, but will have to make it also available on the different server models we support.
We are looking at different git workflows to see which ones suites best our users.
Our preference goes for gitflow, but as it might be a little overkill for our users, we can choose a simplified version like git ship or oneflow
Thatâs a winner. When you pair that in the future with an integrated web server. Bam!
Another winner. Bubble has this but itâs not flexible. You get the meta types predefined by them. Being able to define your ownâŚ
This could open the possibility for an auto-generated bootstrap CRUD table component right? Admin dashboards? BAM. Third winner.
Precisely what I had in mind. 
As for the git workflows I will have a look. Gitflow is kind of defacto solution so I havenât looked much into other lighter ones. Iâll check the links.
Thank you very much @george for taking the time to explain how you are planning on tackling all this. Itâs amazing how transparent you are guys giving enough time to the users to provide input and express concerns(if any).
Kudos!
On a sidenote: funny how this only has 3 votes 
Itâs also great that besides the community votes you also have a future vision for the product and already know where you want it to go.
Itâs clear for me now that you know you want to get from A to B but you are flexible with the path and taking detours to satisfy the users.
This is interesting @George ! The app I am planning to rebuild with Wappler into mobile/desktop UIs will need part of its data stored locally on the userâs device (i.e. emails), but I want all other data stored in the cloud, so multiple users are able to interact with it. I was waiting for NPM/Node to use some of the packages along with something like pouchDB, but will SQLite allow me to store data within the Electron and native apps?
yes - that is actually the most used native storage solution with apps
What about the ability to sync native mobile apps with SQLlite and SQL server/MySQL on the server side for offline syncing or occasionally connected apps?
And if you can build a tool that simply manages table relationships youâll be on to a winner 
I guess this one can be closed?