Here are some features that would massively improve our workflows:
Views & navigation
Any plans for custom group-by views directly in the UX? Being able to save filtered views like in Google Sheets would be huge (bookmarking isn’t cutting it long-term).
Kanban cards and a unified calendar view that pulls from multiple tables would be game-changers.
Could we get an option to use the full navigation bar space for buttons? Right now only 4 buttons show before everything goes to “More”—would love to trade the nav bar for more visible buttons. Further, can we add sections/groups for primary buttons to organize them better?
Forms & detail views
Multi-table forms for complex workflows like invoices/projects (with child table support).
Tabbed detail views to organize child table data better.
Quick copy-to-clipboard for all detail view fields.
Table improvements
More robust filtering with AND/OR logic, ideally with filter options right below column headers.
Manual control over frozen columns.
Drag-and-drop functionality (since it’s already in AppSheet DB, can we get it in apps too?).
SaaS & multi-tenancy
Native support for multi-tenant SaaS apps including SaaS licensing, data partitioning, and app versioning with schema migration tools (even when structures differ between versions). This would really unlock AppSheet’s marketability for commercial products.
AppSheet DB scalability
Current limits feel restrictive for growing apps: 20 tables per database, 100 columns per table, and 200K rows total. Any plans to increase these? Enterprise use cases need more headroom.
Bi-directional schema sync between AppSheet Editor and AppSheet DB would save tons of time.
Collaboration
User comments with @mentions and row history tracking in apps (since it’s already working in AppSheet DB, bringing it to the app side would be amazing for team collaboration).
UX
Can we add the Inter font to the typography options? It’s become a UX standard.
Thanks for keeping AppSheet evolving! Looking forward to what’s coming.
I genuinely think these suggestions could help elevate the overall AppSheet experience for everyone — especially for teams building complex or SaaS-oriented solutions.
Many of these ideas (like multi-table forms, tabbed detail view, advanced filtering, and multi-tenant support) could really streamline workflows and unlock new possibilities for both enterprise and individual developers.
A fine list, but what comes to mind is: why are you bothering? AppSheet has been half-baked for years. Now that AI can write you any app you want without the bother of AppSheet’s multitude of weird limitations, why should this be the year they actually put money into the AppSheet backlog?
@RedVox Thanks for the candid take! I totally get the AI excitement—it’s transforming app development and with MCP servers on the horizon, the potential to enhance AppSheet experiences is massive.
But here’s my honest belief: before layering on those advanced AI capabilities, AppSheet needs to tackle the core backlogs and infrastructure first. These fundamentals are what enable us to build production-grade apps that teams rely on daily.
Only with solid basics can AI truly amplify what we create. On the journey of building Collab I’ve hit enough walls to know they’re holding back real AppSheet enterprise potential. The product team likely sees this too, but consumer voices like this wishlist help with prioritization.
That said, I really like the core of AppSheet. I’m optimistic about its future once these other gaps get addressed too!
Well , I hope your optimism is warranted. Maybe this is the year they look through the backlog of good ideas that have been suggested throughout the years and decide to chip away at them. That would be a surprising but pleasant change.
The main issue is that schema intent between AppSheet DB and the Editor can drift over time.
A few examples:
Enum enforcement mismatch: A `Status` column is created in AppSheet DB as Text. Later, it’s configured as an Enum in the Editor with fixed allowed values. The app enforces the enum, but AppSheet DB still shows unconstrained Text, making it unclear what’s actually enforced.
Reference vs plain text: Columns behave as Refs in the Editor, but appear as simple text fields in AppSheet DB, with no indication of relationships.
Required vs nullable: Fields marked as Required in the Editor remain nullable in AppSheet DB, leading to ambiguity around data integrity.
Rename handling: Renaming a column in AppSheet DB is treated as delete + add in the Editor, which can silently break expressions and dependencies.
Deletion safety: Deleting columns in AppSheet DB can break app logic without dependency warnings.
Even a minimal bi-directional approach would significantly reduce refactoring risk and collaboration friction.
@Jose_Arteaga, there are literally years of accumulated requests from participants of this forum–formal requests, in a dedicated feature-requests forum!–that have never even been acknowledged let alone acted upon, despite assurance by none other than @cschalk_ws. Why might we hope for a different response now? Myself, I find your theatrics insulting, in light of AppSheet’s history. Better to ignore the requests than make a show of entertaining them with no reason to believe anyone with any decision-making capacity cares.
It’s clear that there is a long history here, and I realize that words can only go so far. I am going to bring this specific critique to the product leadership. I intend to be as transparent as possible about what we can and cannot do moving forward, as I know that’s what this community deserves.
I would include improvements to the chat apps feature (or if not then a more integrated way for Appsheet to integrate in the Google Workspace Gmail environment). Like RedVox mentioned this is a good example of what could be a great feature but is half-baked and riddled with bugs and inconsistency.
I’m in agreement with the group here. There’s a long list of features and quality of life improvements that are going un-attended to. AI isn’t solving everything right now and basic feature support is still appreciated.
Please could you add Google Calendar integration onto you list. Of all the features that business need most consistently it is likely to be a calendar for some form of scheduling.
There are ways to work fairly closely with Google Calendar, but they are not simple to implement. It should be effectively native within AppSheet.
Thanks for highlighting this crucial gap, @Alan_Thorp
Google Calendar integration is indeed creator-account only right now, limiting multi-user scheduling workflows.
AppSheet should leverage Google Sign-in authentication to connect directly to each user’s personal Google Calendar via USEREMAIL(). This would enable true multi-tenancy where:
• Users create/read/update events in their own calendars without manual sharing
• Slices like [Owner] = USEREMAIL() become fully functional for personal data isolation
• No more creator-bottleneck for team scheduling apps
This extends naturally to Gmail (per-user inboxes), Drive (personal folders), and Meet (user-initiated calls). Native USEREMAIL() driven connections across Google Workspace would unlock seamless SaaS experiences.
@Jose_Arteaga Could we prioritize OAuth delegation flows where AppSheet handles per-user Workspace API access? Current bots work for creators but break at scale.