What’s missing, named plainly.
We build in the open, and that includes the gaps. This list is curated, not voted on; there are no dates on it because dates on unbuilt software are fiction. When something here ships, it moves to the changelog.
Formsthe big one
The biggest gap on this page, named first on purpose. A form that writes straight into a table — bookings from a website, sign-ups, intake — is how half of this category's real work begins, and Tabla doesn't have it yet. If forms are the thing you need, we'd rather you know before you invest an afternoon. It's the gap we most want to close.
Dashboards
Charts and numbers over your tables. Held until the data side is on par with the best in the category — a thin dashboard on a strong database beats the reverse, but only in that order.
Granular permissions
Roles today are per-database: owner, editor, viewer. We want field- and record-level control — hide the salary field, share one client's records — done carefully, because permissions promised are promises about what people can't see.
Record comments
A quiet thread on a record — who said what about this booking — without turning the database into a chat app.
Formulas that know today's date
Live formulas like "days until check-in" — the kind whose answer changes overnight. Today's formulas compute in the database engine itself, which keeps them fast and always-correct but rules out clock-dependent ones. We want both.
An OpenAPI description
The API is documented and consistent; a machine-readable spec would let tools generate clients and let integrations discover it without reading prose.