The architecture gap: Bridging the disconnect between ASDB and AppSheet UI

I’ve been spending quite a bit of time lately playing around with the AppSheet Database (ASDB). If you caught my earlier post — Elevating AppSheet: A wishlist for the 2026 roadmap — you know I’m still a bit obsessed with getting the “solid basics” right before we start chasing the next big thing.

But as I was tweaking things, I had a bit of a “forest for the trees” moment. I started wondering if we’re building all this incredible power for the wrong people—or at least, if we’re forgetting half of the equation.

The “Admin-only” power trap

The new ASDB interface is snappy and modern. As a developer, I can instantly group data, apply complex filters, and see a full record history. It feels like a professional database. But the second I open the actual app interface, that power vanishes!

  • The “Group by” bottleneck: In the database, I can group by “Status” with one click. In the app, if I didn’t pre-build that specific view, my user is stuck. Why can’t we “pass through” that dynamic grouping ability to the user?

  • The “Filter by” UX: Let’s be honest—the current “Filter” tab in the app isn’t very user-friendly. It feels hidden and requires too many taps. Meanwhile, the ASDB backend has a modern filtering UI that is actually intuitive.

  • Metadata gap: ASDB already tracks who created a record and when it was changed. Yet, we’re still “hacking” together hidden columns and formulas to show an audit trail to users.

Learning from others

I’ve been looking at how other platforms handle this—specifically Odoo (Odoo Studio). They seem to treat features like search, filter by, and group by as “first-class citizens” for the end-user.

In that environment, a user can decide on the fly how they want to slice their data without needing a developer to build ten different “Slices” or “Views” first. It makes the app feel like a flexible, living tool rather than a static form.

Why aren’t we sharing the keys?

It feels a bit like we’re giving the app a brand-new engine (ASDB) but keeping the same old app UI for the user. If the database already has the logic for history tracking and dynamic sorting, I’d love to see a way to just “toggle it on” for the front-end.

I’m curious to hear from others!

Doesn’t the current gap between ASDB and AppSheet UI feel like a bottleneck for your projects? Shouldn’t we be pushing for a more unified experience where the user gets the same dynamic control we see in the backend?

Am I missing something? Would love to hear on this from others.

2 Likes