DataSpeeder is intended to give devs and db admins (who live in the world of power tools like PhpMyAdmin and MySQL Workbench) the ability to provide a simple web GUI for non-admin end-users to view/modify data. So it was intentionally designed without admin-level functionality like editing the database schema directly.
Thanks for the link to your tool, I will look into it.
Actually, one of the (many) features that I (with my coder hat on) would like to implement next is exposing the data via REST APIs. But I (with my manager hat on) need to focus on the specific features that users say are most needed for their deployments.
By the way, let me know if you see an organic way that our tools could work together and complement each other. Partnering would be cool!
Not exactly no-code, but the spirit is the same in what we are building at XgeneCloud. Via our GUI you can scaffold most of the repeatable code that is required in any backend and modify it to your business needs from there on.
* So by just pointing to a database via a GUI, you can generate CRUD-Aggregation APIs (REST/GraphQL) automatically for any given database. It has built in GUI to edit and manage schemas and access control as well.
In last few months, we built[1] a cross platform GUI app that generates automatic APIs over any SQL database.
Here are our key learnings :
* Building desktop apps is made up of an ecosystem which has sub optimal tools and it is very likely that it will never get better. On one end there is Electron which makes it easy to build but then if its a trivial app and your users are not likely to 've faster machines - your users are likely to suffer. Chrome the culprit is pretty much a joke. And on the other end there is QT, GTK which are awful to say the least.
* More than building, it is the publishing these apps that is painful which gets rarely discussed here. It costs you both time and money. By time, on how bureaucratic the process is involved in procuring the SSL from a licensed vendor, its verification and so on. And money to get the code signing licenses which are separate for both MAC and windows. And good luck publishing them without code signing - apss will be treated like malware by OS. However popular apps still go ahead and do this (notepad++ etc)
I would say use electron if you do not have sufficient resources to build natively for every OS. With some webpack optimizations you can squeeze in the app size to less than 300 MB but many electron apps without these optimizations go upto 650+ MB. Or else build it for MAC/Windows - release and see your adoption and take the next step.
I don't have great feedback for you, it's just that I downloaded and ran xgenecloud and was exceedingly confused what to do from the UI that it spawned. It didn't seem clear to me how I could get started, and my options were plentiful; I would've been ok to make a new database thru your UI, point your tool at an existing database, or anything else, but I just didn't have a clear path to querying a schema.
With Hasura, I could run it with about 2 docker commands and build a schema thru their web UI, use GraphiQL in their web UI to query the schema, and read docs to get a clear path on how I might use this artifact in production.
I guess I would just use Hasura if I was you and see what the experience is like vs XgeneCloud, maybe it will show you what I saw.
I hear you - thank you for the feedback. I've got similar feedback from devs who are liking XgeneCloud as well. We are in really early days of our journey - I promise to improve this flow by many folds.
The way it currently works is :
* Each new project has a folder in your filesystem where GraphQL API source code is generated on pointing to database! So when we generate APIs, we also generate source code for those APIs (node.js/express.js) behind the scenes. This is a big leap on how easy it becomes to customise APIs or put some business logic in them
* Thereafter, as and when a developer changes schema (add table, add column etc) - the underlying GraphQL code also gets updated automatically.
Here is a demo of generating GraphQL on postgres & GUI based schema design:
Please see here : https://news.ycombinator.com/item?id=24412737