Request for Metadata API

@zito @Arthur_Rallu

I have asked for this before, but I would like an API that allows access to the app’s metadata.

With the growth of Gemini and other AI services, it is now easy to summarize metadata. This helps us improve our apps.

It would be best if we could update the metadata using the API. However, for now, a “read-only” version is fine. I just need to get the app’s specifications, so please make this available.

Also, the current app documentation is hard to export as the number of features increases. It is not very easy to use with AI services.

9 Likes

I’m working on a Chrome extension that will surface the entire app definition of the app in the app editor.

13 Likes

Thanks @Steve

Act with Confidence: Because the agent operates through your AppSheet app, it is bound by the same logic, security, and governance rules you’ve already built into your enterprise systems. No hallucinations on business rules—just deterministic workflows for consistent, reliable execution.

That’s true—this point is actually quite close to what I’m expecting from the app’s Metadata. I had only been thinking of it as an API for user-facing features, but it might have broader applications. I’d like to give it a try myself.

3 Likes

I have actually had some decent success using agents and just giving them context on the open api spec.

If you own the application, you can just past the following (just replace with your app uuid) in the browser you have the owner’s account open:

https://www.appsheet.com/api/v2/apps/{app-guid-here}/openapi.json

8 Likes

Yes - thanks Steve - this would be incredibly useful - I started working on a plugin for chrome (just a personal one for now) that downloaded the “app definition” in the background and used that via an AI questioning this file. Unfortunately time took over and I didn’t get very far before I had to move to something else.

5 Likes

Biggest problem, once you get a system for this built out, is the sheer amount of text to deal with; the AppSheet definition is… large, and context rot is a thing (see more here: https://research.trychroma.com/context-rot). Building a context management system is going to be key for any tools using Ai.

  • Personally I’ve found success with extracting the definition details from the editor with a REPL tool the Ai can use to digest things
    • This allows the ai to target into the definition details like a laser (vs. a massive dump)

schema extractor

The agent has a tool it can use to query the schema of your app, with maps on where to find key information; this way the ai can figure out what’s going on, in an organic way - like we would - without overloading the context window and falling into the valley of context rot.

Can’t wait to see what people are cooking!

3 Likes

Hi bro Steve, how are you doing? Recently I’ve been focusing on AI-powered coding solutions to gradually migrate my AppSheet applications, so I can expand features and ideas without limitations. As for AppSheet, we’ve talked a lot about the expected improvements, the bugs that have been reported year after year, and the essential features needed in the AI era that still haven’t been integrated. But it seems like Google’s dev team is busy working on AI.

So for now, I’m just maintaining the apps that are currently running and slowly preparing to move away from the platform. I only hope that AppSheet keeps the system stable and bug-free, without needing to add anything new—because the new features they’ve released recently are like a drop in the ocean; creators and users don’t really need them.

3 Likes