| If I am weighing up: * Complete no code - Bubble * Out of the box code - Next.js etc. * Code - Node JS / Express etc. * Canonic Where do you fit in? Who chooses you over the other options? Because the disadvantage of yours is lock-in / pricing / up-skilling to a non-standard way. Same problems as many others - Bubble.io etc. There must be some killer win you get from using this. Bubble lets people who have never coded build a rough MVP, maybe get some orders, so I can see why people fork up the $ and struggle through that UI, because the alternative is a 4-5 figure fee from a freelance programmer. But I don't think Canonic avoids code as you still need to do the front end. (Maybe that's it? You create a front end version of Canonic next?) So I'm interested in who will buy this and why. |
Out of the ones mentioned, we are probably closest to Bubble. However, as you rightly said we are currently focused on the backend API building problem.
As we've been pivoting to be a more citizen-first non-tech friendly platform, frontend on Canonic is something we have been discussing and debating frequently.
The main concern with a frontend builder for us is the need for it to truly be as close to a design tool as possible. The frontend of an application frequently ends up being unique to accommodate branding and creative freedom and becomes hard to fit in a traditional drag-n-drop tool. We just want to make sure, we are truly solving that problem and not just making another frontend builder that people have to wrangle to get their designs to fit.
As for lock-in, we do want to avoid it all costs and our working on strategies and features that would allow you to migrate in and out of Canonic with ease.
Currently, Canonic is a great fit for anyone who wants to build a backends quickly and without writing code. Some level of technical know-how is, however, required. We do hope to eliminate that soon.
P.S. Canonic plans to have a free forever plan for getting started and hobbyist projects