Live data from Hacker News

Form to DB

formtodb.com

31–40 of 129 posts

Re: Form to DB

#31
post #30

Form to db is simple task, the hard part is the table.

Agree, the table is the component we’ve spent the most time building: https://retool.com/components/table-new

This links to the legacy table component.

Which should I use for new projects? I assume the new one?

Re: Form to DB

#32
post #21

As a side note I found retool to be the most prohibitively expensive out of 6-7 solutions I was researching for “low code admin app builder” ecosystem.

Hm, sorry you found us to be expensive. Two notes: * Forms (ie the product here) is free. * We’ve always aimed to build a sustainable business where we charge reasonable prices and can guarantee we’ll stay in business ourselves. It’s true there are other products that are cheaper, but every single one of those companies is unprofitable and many will probably be dead in a few years. See, for example, Airplane, Interva…

Just wanted to echo I love your product but the pricing is too prohibitive. My use-case is wanting to offer a dashboard to my own clients. But the business pricing was $50/mo per user and also gave each user editor privileges.

I want to create customer accounts, apply settings (e.g. I delimit the data their account can access, basically adding WHERE clauses on a per-account basis), and they can access white-label read-only dashboards with their own user/pass.

Retool seemed 100% insistent on being an internal-only tool with a high cost per user.

Re: Form to DB

#33
post #21

Earlier quoted context omitted.

Hm, sorry you found us to be expensive. Two notes: * Forms (ie the product here) is free. * We’ve always aimed to build a sustainable business where we charge reasonable prices and can guarantee we’ll stay in business ourselves. It’s true there are other products that are cheaper, but every single one of those companies is unprofitable and many will probably be dead in a few years. See, for example, Airplane, Interva…

Just wanted to echo I love your product but the pricing is too prohibitive. My use-case is wanting to offer a dashboard to my own clients. But the business pricing was $50/mo per user and also gave each user editor privileges. I want to create customer accounts, apply settings (e.g. I delimit the data their account can access, basically adding WHERE clauses on a per-account basis), and they can access white-label rea…

Pricing is always tricky. One pricing never fits all use case. So we have worked hard to offer pricing options like usage based pricing/ dev based pricing in addition to user based pricing.

Was curious to apply your use case and see if our pricing model maximises ROI.

Disclaimer: I am co-founder at a retool alternative platform for building internal tools and enterprise apps.

Re: Form to DB

#34
post #30

Earlier quoted context omitted.

Agree, the table is the component we’ve spent the most time building: https://retool.com/components/table-new

This links to the legacy table component. Which should I use for new projects? I assume the new one?

Sorry just updated!

Re: Form to DB

#36
These types of projects always remind me of MS Access. Access is forms on a database, and really easy to use. It obviously has its drawbacks but nothing has come close to it. I've never understood why MS didn't capitalise on it by extending and improving it.

Re: Form to DB

#37
post #21

As a side note I found retool to be the most prohibitively expensive out of 6-7 solutions I was researching for “low code admin app builder” ecosystem.

Hm, sorry you found us to be expensive. Two notes: * Forms (ie the product here) is free. * We’ve always aimed to build a sustainable business where we charge reasonable prices and can guarantee we’ll stay in business ourselves. It’s true there are other products that are cheaper, but every single one of those companies is unprofitable and many will probably be dead in a few years. See, for example, Airplane, Interva…

As someone who also tried and really liked Retool but also found it too expensive I can add my reasoning.

I help companies with digital transformation, what it usually entails is deploying solutions to small teams and then growing them as we get buy in from the business. The initial users are high frequency users of the tools, and later users might be infrequent users.

The problem I found with Retool was that as I scaled to the infrequent users the cost per user remained static, so I would be punished for my tool becoming more popular.

Re: Form to DB

#38
Crazy prices. I'm always wondering for what kind of companies things like Retool are. Internally, when we want to whip up a crud app, we use Nextjs with T3 stack and you are up and running in two-three hours.

Re: Form to DB

#39

These types of projects always remind me of MS Access. Access is forms on a database, and really easy to use. It obviously has its drawbacks but nothing has come close to it. I've never understood why MS didn't capitalise on it by extending and improving it.

Because the single-system paradigm doesn't work any more. However, modern replacements do exist, Airtable is one of the first; it's basically the notion of a "spreadsheet with more structure", and then building forms and such on top of that. I've recently been playing with Grist and like it, although it is rough around the edges.

https://www.getgrist.com

Re: Form to DB

#40
post #21

As a side note I found retool to be the most prohibitively expensive out of 6-7 solutions I was researching for “low code admin app builder” ecosystem.

Hm, sorry you found us to be expensive. Two notes: * Forms (ie the product here) is free. * We’ve always aimed to build a sustainable business where we charge reasonable prices and can guarantee we’ll stay in business ourselves. It’s true there are other products that are cheaper, but every single one of those companies is unprofitable and many will probably be dead in a few years. See, for example, Airplane, Interva…

Dynaboard shutting down does not relate to pricing for end-users.

From a Low Code product perspective, we were still able to build a beautiful and functional product. Our product unit/engineer ratio is much higher than our competition (see, for example, Retool), which allows us to provide the best value for our users. Regarding the transition, I don't see any indication from the note you posted that users will have to rebuild all their apps. Rather, the founder is saying he will provide more information and possible steps. Who knows – maybe it would be integrated into Figma? And Figma would gain great runtime and IDE capacities?

Post reply on HN