[hchua]

Hi, this looks really cool - slick UI and clear value proposition. Great job!

Just a couple of questions:

1) why the emphasis on “for MVPs”? It seems like it can be used to build a proper product long term. Adding “for MVPs” make it seem like end users should expect to redo whatever they’ve done if they get any traction.

2)How does this compare to Retool (or how do you intend to differentiate it)?

[mion]

1) It is in fact possible but as noted previously, most people still wouldn't feel comfortable running their core business long-term on this kind of tool. However, no one worries about running their business on AWS and in fact our infrastructure is on top of them (like Heroku). So we need to grow a bit more before people are OK with that :)

2) Retool is tailored at internal tools, so you can't quite customize the UX as you'd want for something that is touching end users. Besides, it's quite expensive for the MVP use case because they price per user (we don't, our pricing page is coming soon).

[Closi]

I would prefer to use this sort of things for longer term but non-core functions (e.g. back office).

I agree with OP that it's a weird use case, as a focus on short-term MVP may limit user retention if you actually succeed (or is the idea that people will accidentally start to use it long term?).

[dinkleberg]

Retool is a cool product but it’s for a different use case. Retool is for building internal applications, this is for building MVPs.

And I assume they are focused on MVPs because you aren’t going to run a $10m company on a no-code solution, you’re going to have your own devs. But using a tool like this can help you build your business while you get to that point.