bieberChen

I use nestjs in my open source no-code database https://github.com/teableio/teable, and I really like it, especially the dependency injection capability.

We have a plan to do it, we have a lot of user feedback, and we find it very useful

Can you share the detail? you mean cant deploy on mac?

search ”In the comments” in this page

Fixed~

There is currently no "join" capability, but there is a "Link Field" to handle table relationships.

We also found the calendar view useful, as it sits in the middle of the requirements priorities

Teable can currently share forms to get data from external users. You can also integrate with other lowcode tools to build external application interfaces

you are right, I'll fix it~

In the SingleLineText field, you can choose to show as email, Any format verification (regex) will be introduced in the future.

It's kind of like collaborating directly on a database (Through the Grid that has been prepared) rather than building an application interface

This pun is interesting; the 'new' in Teable is literally the 'e'. I've addressed the product comparison questions in a public reply, hoping it's helpful.

In the comments, everyone is interested in the core differences between Teable and similar products. Here, I'll compare the products mentioned. Please note that since I'm not a deep user of the other products, there might be inaccuracies, and I welcome corrections.

Grist

I had heard of Grist before but never actually experienced it. A quick look at Grist through videos showed that its dynamic spreadsheet capabilities are incredibly powerful, complete with fixed field types, making it excellent for organizing structured data. It seems to have an edge in flexibility, and compared to Airtable, it might be more akin to Smartsheet.

According to its official documentation, Grist's Pro Plan offers up to 100k rows, indicating that queries and calculations are processed on the frontend or in memory, which typically makes it challenging to scale data rows further. This is a problem that Airtable also faces.

Baserow and NocoDB,

my impression is that Baserow's features are relatively more stable, and it started commercializing earlier, being among the first batch of open-source Airtable alternatives.

Baserow initially had a limit on the number of rows, but this year's updates seem to have significantly increased its data capacity. Notably, Baserow does not support Bring Your Own Database or query by SQL, but it offers a seamless scrolling table interface, unlike NocoDB, which requires pagination. In terms of other functionalities, both have their strengths. My assessment aligns with what I found on Baserow's official forum and comparisons with NocoDB.

Teable Compared to similar products, Teable invests heavily in its table format UI, striving for seamless scrolling, copy-pasting, batch editing, and other quick table operations, which we believe are key to saving users' time. Therefore, we developed our Canvas table rendering component to achieve perfection. Meanwhile, batch operations pose a significant challenge for database compatibility, but we see this as a necessary investment.

Additionally, Teable supports developers by offering open database connections and database permission management, a concept inspired by Supabase. This allows both developers and users to create on the same platform.

What we think the future of no-code products look like

1. An interface that anyone can use to build applications easily.

2. Easy access to data, letting users grab, move, and reuse their information as they wish.

3. Data privacy and choice, whether that's in the cloud, on-premise, or even just on your local.

4. It needs to work for developers too, not just non-tech users.

5. It should handle lots of data, so it can grow with your business.

6. Flexibility to integrate with other software, combining strengths to get the job done.

7. Native AI integration to takes data automation to a whole new level.

Thank you!

Sure we will, this week.

I'm truly sorry if our actions have caused any offense. Our team consists of 5 freelance programmers without any designers on board, and without any funding, so we had to tackle the design aspect ourselves. Initially, we planned to use a colorful gradient theme, but found the UI coordination too challenging for us. It was then that we came across the beautiful simplicity of shadcn, and decided to go with a black and white theme.

We did look at various black and white themed websites on the market, including Notion and Attio, but I assure you, we did not plagiarize any images. Thank you for your critique. We will make it our priority to adjust our design to be more unique as swiftly as possible.

Don't worry, it's been noted!

NocoDB is a pretty impressive product. In fact, the idea for creating Teable emerged around the same time NocoDB was released. The challenge with Teable is our desire to provide a fully No-Code and real-time collaborative experience on the product interface, which contrasts with NocoDB's approach of exposing more database details to the user. Both have their pros and cons.

Additionally, Teable supports developers by offering open database connections and database permission management, a concept inspired by Supabase. This allows both developers and users to create on the same platform.

That is what I want to share. When users create fields in the visible table, it directly creates columns in the corresponding Postgres table. There's a mapping between the fields on the UI and the physical columns. At the same time, relationships are a major highlight; the "link field" of the Teable will create logical foreign keys or junction tables between physical tables to maintain the relationship.

I must say, this suggestion is fantastic, super grateful!

In fact, we haven't seriously discussed commercialization yet; our main focus is on perfecting the basic functionalities. But I believe the price will definitely be very reasonable.

In fact, Teable has no limit on the number of rows; you can always trust Postgres . Here's a table with 1 million rows [0], where you can experience the response speed as well as the feedback from filtering and sorting.

[0]: https://app.teable.io/share/shrVgdLiOvNQABtW0yX/view

GlideGrid is an outstanding canvas grid component (interestingly, it was initially used by us before we decided to create our own version to enhance the user experience). Teable, on the other hand, is a fully-featured no-code platform aimed at empowering those without technical backgrounds to efficiently work with Postgres (a relational database).

If I understand correctly, this feature is currently supported. You can try the Sales CRM template https://template.teable.io/t/recHJEzSkIZ1IpjltNZ . In the first table named Opportunities, if you expand the first row, that might be exactly what you're looking for.

A more optimal approach is to utilize the SDK to use the table as a React component within the application. This capability will be iterated later. Teable's UI interface is all built on top of a standalone SDK. In theory, both component and collaborative capabilities can be exposed externally, but it will take some time.

Technically feasible, if you deploy Teable under the same domain with your own app, the user sessions can be shared then you can use an iframe to embed the table into your application, and backend services can access table data within Teable through SQL or API.

I'm thrilled to hear that!

I build a better one https://teable.io/ and plan to open source it next week