Appsmith

What do you like best about the product?

Drag-and-drop UI components.
Built-in JavaScript support for logic.
Role-based access control (RBAC).
Self-hosted or Cloud options.
Community-driven & active support.
Very easy to connect with SQL, REST APIs, GraphQL.

What do you dislike about the product?

UI customization is limited (compared to pure frontend code).
Large datasets can slow down widgets if not optimized.
Requires backend queries for complex logic (limited frontend-only solutions).
Manual work is still there like binding and logic building

What problems is the product solving and how is that benefiting you?

Appsmith is helping me solve the problem of building internal admin dashboards and management tools quickly without spending a lot of time on frontend development.

Instead of building everything from scratch, I can easily connect my database (PostgreSQL), write custom queries, and design a functional UI using drag-and-drop widgets.

This saves a lot of development time and allows me to focus more on business logic rather than UI boilerplate.

It’s also helping my team by making non-technical users easily manage data (like users, transactions, roles, etc.) in a safe and controlled environment without giving them direct database access.

What do you like best about the product?

Being able to connect to datasources and present the data in a table is quick and easy.
Creating compex forms is also straight forward, having the flexibility to add javascript code is very useful.
Also there is a large number of widgets to use which makes it possible to provide great functionality in your apps.

What do you dislike about the product?

its hard to find anything to dislike at this early stage, there is a big learning curve but it is worth it to be able to build apps quickly

What problems is the product solving and how is that benefiting you?

I hope to be able to estimate quicker development times and build complex apps that will save clients money.

What do you like best about the product?

It is useful, it supports the usual use cases of a CRUD. So far, I haven't found anything it can't do. The connectors with API and database are very well supported. In one day, I migrated a simple app from a React (Vercel) + Railway (MySQL) world to appsmith. Amazing!

What do you dislike about the product?

The little separation that exists between data layers and presentation. By playing with parameters, you can isolate, but there is quite a bit of coupling.

What problems is the product solving and how is that benefiting you?

Complexity problems, appsmith simplifies them and focuses on data entry.

What do you like best about the product?

I create apps for internal teams quickly to support business processes we need to execute

What do you dislike about the product?

It can still take some time to learn the inner workings.

What problems is the product solving and how is that benefiting you?

I create internal apps for business processes I need to automate while giving users a UI to the process

What do you like best about the product?

I managed to build a personal finances app with a good deal of features literally from day 1, exploring on the AppSmith free plan connected to a Supabase DB. I also explored AppSheet and Budibase for the same project before, but my experience was far inferior with these alternative and I wasn't able to reach a reasonable progress in the time I was able to spend.

The speed of development is incredible and I was able to navigate my way through by only spending a few minutes on tutorials when getting blocked. The concept of having managed queries (as wrappers over the DB) makes a ton of sense, as well.

I tested so far the integration with a PostgreSQL relational DB in Supabase and the experience of setting this up was also very smooth (including the usage of the Deno framework).

It is marvelous how AppSmith combines ease-of-use with power, given that almost everything is parametrizable with JavaScript behind the scenes. Apps are never straight-cut, and my experience with low-code/no-code tools before was that I hit a roadblock where I would have needed to write a bit of code to achieve my goals.

Such a comprehensive set of features, a UX first focus and the ability to freely extend the funcitonality are for me huge wins!

What do you dislike about the product?

Getting aligned to the best practices (in order to scale your efforts down the line) takes time, but that is the proper design time that needs to go behind any engineering endeavor.

What problems is the product solving and how is that benefiting you?

- productivity from day 1
- extensibility/customizability for those 5% of the requirements that are usually hard/impossible to cover by plan low-code/no-code tools
- generous free plan to start with
- robust UX