Ask HN: Does anyone find tools like Retool useful?

2 points by swman 2 years ago | 9 comments

Hey folks, I must be the wrong audience for a tool like Retool but after showing it to my friend who isn't technical, I still don't understand who this tool is for.

My friend didn't have a clue looking at the UI what to do.

Looking at them work, it was clear they had to know a little beyond the basics of databases, javascript, and html/css to even make sense what they were looking at.

As for me, I knew what was going on but then I was thinking why would I ever use this as someone that is experienced full stack SWE.

Personally it reminds me a lot of Notion. It is pretty approachable for nerds like me but I have never seen anyone else use any of the power features like databases or all the cool pivot type views that are possible. I have a handful of friends who use it and they say they just use it for notes, which is fine but that's like 10% of its usecases.

So... is anyone actually using Retool or similar tools for something meaningful? And what are you doing with it if I may ask?

kinj28 2 years ago |

So as a full stack engineer - don’t you find time saving as a good enough reason to use tools like retool to put a decent frontend across with very less efforts?

FWIW- I run growth at DronaHQ ( retool like tool )

swman 2 years ago | |

Hm.

So again forgive my ignorance here. I formerly worked at a unicorn startup that exited some time ago, so I've not worked at FANG or something huge like that, but definitely at a company that needed to pump out tons of features fast for both internal stakeholders and external users.

For user facing stuff we eventually developed a design system so fair enough, don't need retool or something there.

For internal facing stuff, before our design system was built, we'd literally just use mui (or bootstrap, or even bare bones) and react and put together whatever tool Sales/support/etc. needed and it would be live in like a couple hours max. I could access any streams or databases easily, and put a simple UI around whatever. Things like a need to load up customer information from sfdc instance A and cross reference it against data in live customer db, and call out any data (like phone/email,etc.) that didn't line up.

Wouldn't it be easier for a full stack engineer to just code it? Or am I missing something? I mean drag and drop + set up interactions + pull from database + write to database + other things via a UI seems more time consuming than just writing 100-200 lines of code.

How do I get access to my customer database in this tool and salesforce instance? What if I need to check a user's account information via our account service to see if they have access to some additional paid features? Would I even want to connect a live data store to this kind of tool?

Sorry if I'm rambling, I am just confused if this is a valid use case or not. Or is it just to make basic forms?

ruslan_talpa 2 years ago | | |

Over the time (as part of researching competition) i also hear a lot of fans of retool with rave review (though never specifics as to what they are using it for). And i get it's appeal for building the UI, drag and drop, you see it directly and all the props of all components are there in the UI with documentation. But putting together the UIs is not what i find hard (using libraries like Reach-Admin). For me it seems way more time consuming having the UI interact with the actual backend/db and when i see in retool that this is done by "write a bunch of SQL for each table/button/screen" and they are just there in a list ... i just don't see how this is scalable/manageable for a internal tool with 10-20 screens. Also all the input validation is on the frontend ... did i miss some docs somewhere?

kinj28 2 years ago | | |

A response to your use case:

- you deploy an on prem instance of the tool - you just connect to the data sources like sfdc or sql or whatever data sources via the connector layer - you drag drop and build Ui super fast and bind data in a jiffy

Net net - your time saving would be around:

1) no need to create APIs or anything to connect to your customer db 2) no need to figure sfdc custom APIs 3) no need to add any specific DB sdk in your app and figure using them 4) build Ui real quick. 5) write your cron jobs or microservices really

neximo64 2 years ago |

I know alot of people using Retool and it is almost invaluable.

It's meant for technical people who don't know how to code.

swman 2 years ago | |

That's awesome! Can you give a little more insight? Like I said I'm curious to learn how people are using it.

I am definitely not the audience for it so I'm trying to understand. Thanks

neximo64 2 years ago | | |

Think of a business/analyst/marketer type person who knows Excel, SQL (or can use ChatGPT), and knows roughly how everything works. They want to do things but dont know how to code, or they do but in such a way its too simplistic.

KomoD 2 years ago |

Yep, I use it for simple internal tools, don't wanna make a bunch of frontend stuff myself