App SDK: Build custom content experiences on Sanity
发布时间:2026-11-06 | 浏览:1
Custom editorial interfaces
Build custom tools for your team with built-in authentication and one-command deploy. All using react hooks.
AI-ready tooling When you combine App SDK with Content Agent, you can create smarter workflows for your content team. Ready to use on day one.
AI-ready tooling
When you combine App SDK with Content Agent, you can create smarter workflows for your content team. Ready to use on day one.
Authentication included Apps inherit Sanity's auth. Roles, permissions, and access control work out of the box. No separate user management.
Authentication included
Apps inherit Sanity's auth. Roles, permissions, and access control work out of the box. No separate user management.
Real-time by default Every edit syncs instantly through the Live Content API. Your team sees the same data, always current. No polling. No refresh buttons.
Real-time by default
Every edit syncs instantly through the Live Content API. Your team sees the same data, always current. No polling. No refresh buttons.
Custom fit to you Use your component library, your design system, your brand. App SDK handles the data and sync so you own the pixels.
Custom fit to you
Use your component library, your design system, your brand. App SDK handles the data and sync so you own the pixels.
App SDK is React. If you know hooks, you know this.
Three hooks handle most of what you need:
useDocuments to fetch filtered collections
useDocument to read a single document that stays current
useEditDocument for optimistic writes that sync to Content Lake
Developer experience
Typegen turns your schema into types automatically
Vite dev environment for fast iteration and hot reload
Deploy with a single sanity deploy command
Some workflows need their own interface. Build focused content apps for exactly one job.
Translations dashboard Filter untranslated content, batch-select for translation, and track locale status from a single view.
Translations dashboard
Filter untranslated content, batch-select for translation, and track locale status from a single view.
Marketplace feeds Assign products to marketplaces, track publish status, and keep feeds updated without spreadsheets.
Marketplace feeds
Assign products to marketplaces, track publish status, and keep feeds updated without spreadsheets.
App SDK is typed React hooks on top of your content model. AI tools already know how to write React. Give them your schema, and they know how to write your app.
"Build me an app that shows all our store locations in a grid, with their hours editable inline. Group by region and highlight any stores with missing hours."
What makes it work
Your schema provides the types (stores, hours, regions)
The SDK provides predictable patterns ( useDocuments , useDocument , useEditDocument )
You provide the requirements; AI connects the dots
The result: Working code that matches your content model, not generic boilerplate you have to rewire.
Custom apps isn't just where content lives — it's where work gets done. Trigger translations, approve publishes, route products to marketplaces, all without leaving the editor.
The infrastructure advantage
Real-time feedback lets editors see automation status update instantly. No polling. No "check back later."
Inherited permissions mean the same roles control both content access and action triggers. No separate auth system.
Content as state means your documents are the workflow state. A translation's status lives in the document. An approval flag is a field. No shadow database to sync.
Extend your editorial workspace →
Make your app AI-context aware →
Run server-side logic at scale →
The structured content layer underneath →