Retool

My main use case for Retool  involves an inventory app project. I built a mobile app to make an inventory of chemistry products. Retool  helped me with that project as it was a good way to show a quick solution to call APIs for another software, the main software for chemical products, and Retool has good possibilities for this purpose.

I found working with those integrations to present some challenges, but not really difficult challenges because Retool integrates functionality to call APIs and manage the results to provide data to mobile app components.

I have another main user story to add about my use case and experience with those integrations in Retool. We have to scan QR codes and the scan has to be made with Zebra hardware.

The best features Retool offers include the ability to quickly create a mobile app and use this mobile app in a native mobile app for Android.

I found the process of creating and deploying those mobile apps for Android with Retool to be smooth as the documentation is very good, and I found answers and examples to create a mobile app. I can access a debug mode in the mobile app which was really convenient to make tests and find what can be improved, where I have a problem, and how to correct it.

Retool positively impacted my organization as the proof of concept we built gave us a way to convince power users and key users before developing the real software. It was a way to maintain the launch date of the project, which helped speed up the project timeline and save resources.

Retool, being a low-code/no-code platform, could improve by allowing users, particularly non-technical users, to use it more easily.

In the mobile app development, you have to use JavaScript to interact with components, and for non-technical users, it's already too technical, so Retool has to add some integrated solutions.

I have been working in the IT sector for 26 years.

Retool is stable in my experience, but I did have an issue with my app where I lost some modifications and had to recreate some functionalities.

I don't think I reached out to customer support, so I cannot comment on my experience.

I did not previously use a different solution before Retool, although I had explored several solutions.

I think we can see time saved to start the proof of concept and maybe money saved because I was able to develop the mobile app alone without needing additional resources.

The pricing, setup cost, and licensing experience were good as the free plan was enough for us.

I evaluated other options before choosing Retool; I talked with no-code experts and found KHAR, K-H-A-R, could be a way, along with Zilio, another French app development solution.

My advice for others looking into using Retool would be to follow JavaScript training if needed and take time to train yourself with Retool.

Before wrapping up, I would like to add that I think Retool is a solution to know about because I don't find anything totally comparable in the market.

I found this interview to be a bit quick, and I have to think about my answers, maybe because I'm French and English is not my natural language. I would rate this review a 7 out of 10.

I use Retool  to create jobs and workflows, managing whatever assigned tasks are there to create jobs and upload data entries.

Whenever I begin my analytics work, I first create a job using Retool  by uploading my Excel file so it gets processed, and then the output comes from another dashboard linked with Retool, acting as a filter that sorts our data for the web and our other software.

I also use Retool to download data from our company's data repository, from where I can compare my data to check its correctness or whether we need to feed that data into our reports for the desired results.

While I don't think there is a best feature in Retool, the way data appears in Retool is pretty good, allowing us to see, sort, download, or review required fields for our use case, and the customization options are beneficial, allowing us to tailor features to our needs.

Retool positively impacts our organization by saving costs compared to using other data repositories, and teams prefer Retool for daily tasks that perform customizations to showcase web pages or link their data backend, making it more efficient and cost-effective than other software available in the market.

The UI of Retool could be improved, as I am not fond of the current design, and there should be a platform for learning how to use Retool efficiently, especially since our software team customizes it for their needs, leaving the operational team with limited knowledge on how to customize it.

Since I haven't delved deeply into Retool beyond exporting data, I believe it could benefit from tutorials or learning platforms on how to integrate Retool into daily tasks, as more feedback might arise from that knowledge.

There should be better documentation or support for non-technical users, providing a platform to learn and implement Retool effectively.

I have been using Retool for the past three years.

Retool is stable, and I haven't encountered any downtime or issues.

Retool's scalability appears to handle growing amounts of data and users easily.

I haven't reached out to customer support, so I can't comment on my experience with them.

This is my first time using any solution, so I haven't used a different one before Retool.

I have no idea regarding pricing, setup costs, or licensing.

I haven't evaluated any other options before choosing Retool.

I don't have specific answers regarding cost savings or increased efficiency.

For mesh regeneration, we have reduced time for our model; apart from that, I don't have much knowledge to share.

For managing your work or creating tasks, Retool is the best option you can explore, and you should definitely give it a try. My overall rating for this product is 7.