How is that different from rapid development? How is this process even sustainable? How do you ever get beyond an MVP this way? How is tech debt accounted for?
Also, have you seen a lawyer about the implications of selling that process as a franchise? This would mean everyone subscribing to your process would be forced to be your subcontractor. I don't see this happening in the software world, really.
Did you try our product? There's a link in the article. It reads meta data from your database and automatically wraps your database into a CRUD Web API. The point is that such things can only be achieved if you super standardise things, which kind of resembles the way McDonalds are creating burgers, and the way Toyota are creating cars for that matter.
Thank you for answering; so it's just the simple CRUD APIs that you provide for the price of subsidizing one's own business by becoming a franchise?
Also, if I'm not mistaken, there are already things like supabase, which make it incredibly easy to create such APIs directly from the database, and they don't require you to adhere to that much standardization, offering more flexibility at the price of defining the API surface yourself, but it's probably still a better solution in the long run, as you'll hit limitations much easier with automation.
It's much more than a simple CRUD API wrapper. If you want to compare us with SupaBase, the best way to compare is to try to do anything but reading stuff from your database, such as sending an email, connect records to payments, implement translations, etc, etc, etc ...
To put that into perspectives, we built our entire middleware infrastructure ourselves using our own tools ...
we built our entire middleware infrastructure ourselves using our own tools ...
Which just shows that your tools are suited to fulfil your use case, not everybody else's. And you still haven't answered my criticism about defining this as a franchise.
How is that different from rapid development? How is this process even sustainable? How do you ever get beyond an MVP this way? How is tech debt accounted for?
Also, have you seen a lawyer about the implications of selling that process as a franchise? This would mean everyone subscribing to your process would be forced to be your subcontractor. I don't see this happening in the software world, really.
Did you try our product? There's a link in the article. It reads meta data from your database and automatically wraps your database into a CRUD Web API. The point is that such things can only be achieved if you super standardise things, which kind of resembles the way McDonalds are creating burgers, and the way Toyota are creating cars for that matter.
Thank you for answering; so it's just the simple CRUD APIs that you provide for the price of subsidizing one's own business by becoming a franchise?
Also, if I'm not mistaken, there are already things like supabase, which make it incredibly easy to create such APIs directly from the database, and they don't require you to adhere to that much standardization, offering more flexibility at the price of defining the API surface yourself, but it's probably still a better solution in the long run, as you'll hit limitations much easier with automation.
It's much more than a simple CRUD API wrapper. If you want to compare us with SupaBase, the best way to compare is to try to do anything but reading stuff from your database, such as sending an email, connect records to payments, implement translations, etc, etc, etc ...
To put that into perspectives, we built our entire middleware infrastructure ourselves using our own tools ...
Which just shows that your tools are suited to fulfil your use case, not everybody else's. And you still haven't answered my criticism about defining this as a franchise.
If you want to pick a fight, go pick somewhere else mate - I'm not interested ;)
And you're not interested in criticism. Figures.
Not really. If you disagree with me write your own article 😉