Sitecore App Studio Overview for Developers

If you have been keeping an eye on Sitecore AI , you have probably noticed App Studio popping up everywhere. It is the part of Sitecore Studio built specifically for developers and partners who want to extend the platform with custom apps and extensions using Sitecore's APIs, SDKs, and supported integration standards.

For years, SaaS meant a trade-off. You got speed and scalability, but you lost the ability to shape the platform around your business. App Studio changes that equation. This results in a platform where developers can create custom features that work effortlessly within SitecoreAI without compromising on the ease of use and security that comes with SaaS.

In this post, we will explain how App Studio functions, how its components interact, and everything necessary for creating your first app. For the official breakdown of how these components fit together, see Sitecore's Studio overview documentation.

1. What App Studio Actually Is

Use case: You need a way to build custom functionality that lives inside the SitecoreAI interface instead of as a disconnected external tool.

Overview: App Studio is one of four components inside Sitecore Studio (alongside Agentic Studio, Sitecore Connect, and the Marketplace). It lets you configure custom or public apps that run inside SitecoreAI using the Marketplace SDK, REST APIs, and GraphQL.

Sitecore Studio

├── Agentic Studio → AI workspace for marketers

├── App Studio → build and configure custom apps and extensions

├── Sitecore Connect → system-to-system connectors

└── Marketplace → discover, install, publish apps

Benefits:

• Apps run inside the Sitecore UI, not as bolt-on external tools
• Built on open standards: APIs, SDKs, and supported integrations
• Apps can stay private to your org or publish to the Marketplace

2. Setting Up Your First App

Use case: You are ready to register a new custom app for your organization.

Overview: Creating an app starts in the Cloud Portal under App Studio. You name it, choose your extension points, decide on API access, and set a deployment URL for local development.

Cloud Portal → App Studio → Create App

- App name

- Extension point(s): standalone / fullscreen / dashboard widget /

  Page Builder context pane / custom field

- API access: select required Sitecore APIs

- Deployment URL: http://localhost:5173 (Vite) or

  http://localhost:3000 (Next.js)

Benefits:

• Simple setup with no infrastructure overhead
• Extension points map directly to where users will see your app
• Local dev URLs make iteration fast before you go to production

3. Working with the Marketplace SDK

Use case: Your app needs to talk to Sitecore and run securely inside an iframe within the platform.

Overview: The Marketplace SDK provides the secure context and communication mechanisms needed for apps running within the Sitecore platform, and can enable authorized access to supported Sitecore capabilities and APIs based on the app's configured permissions.

import { ClientSDK } from '@sitecore-marketplace-sdk/client';

async function initApp() {

  const client = await ClientSDK.init({ target: window.parent });

  client.query('application.context')

    .then((res) => console.log('App context:', res.data))

    .catch((error) => console.error('Error:', error));

}

initApp();

Note: Refer to the official Sitecore Marketplace SDK documentation for the latest initialization syntax and available query operations.

Benefits:

• Provides contextual information appropriate to the selected extension point, which may include tenant, Sitecore context, or selected-item information
• Handles the secure communication layer so you do not build it from scratch
• Works the same underlying pattern whether your app is fullscreen or embedded in Page Builder

4. Extension Points Explained

Use case: You want your app to show up in the right place for the right workflow.

Overview: Where your app appears depends entirely on the extension point you choose. Each extension point can expose context relevant to its host environment and workflow.

• Standalone – opens as its own page
• Fullscreen – runs across the full tenant view
• Dashboard widget – embeds into the SitecoreAI dashboard
• Page Builder context pane – shows alongside content editing, with access to the selected item
• Custom field – renders inside a specific field type

Benefits:

• One app, multiple entry points depending on user need
• Context is scoped to what each extension point's host environment supports
• No need to build separate apps for separate workflows

5. Publishing to the Marketplace

Use case: You developed something useful and now want to distribute it beyond your organization, or make it available to specific partner companies.

Overview: After testing the application, you can keep it private, share it with select organizations, or publish it to the Marketplace. Always confirm the current visibility options in the Cloud Portal, as configuration screens can evolve over time.

App Studio → Select App → Publish

- Private: visible to your org only

- Shared: grant access to specific orgs

- Public: list on the Marketplace

Benefits:

• Flexible visibility controls
• Public apps build credibility in the Sitecore ecosystem
• Helps developers demonstrate technical expertise and contribute to the broader Sitecore ecosystem

Best Practices

• Start with the Marketplace Starter Kit instead of building your SDK integration from scratch
• Match your extension point to the actual user workflow, not just what's easiest to build
• Request only the API access your app genuinely needs
• Test locally against your deployment URL before touching production
• Keep private apps private until they are genuinely ready for wider use
• Document your extension points clearly if other teams will build on your app later

Wrapping Up

App Studio is Sitecore's answer to a problem developers have quietly dealt with for years: how do you get SaaS convenience without giving up the ability to build what your business actually needs? It closes that gap by putting real developer tools directly into the SitecoreAI ecosystem.

The process is basically the same whether you are creating an internal app or a public Marketplace app: register your app, select extension points, integrate via the Marketplace SDK, and launch. It is one of the more approachable enterprise platform extensions models we have worked with so far.

Written by

Meet Shah

Sitecore Expert

I’m Meet Shah, a Sitecore Certified Software Developer at Arroact Technologies. I work with Sitecore XP, Sitecore Order Cloud, and .NET to build digital experiences that connect content, commerce, and data in a way that actually makes sense for users and teams. 

I’m especially interested in how Sitecore AI can be used to create smarter, more personalized experiences. I like exploring how small improvements in logic or structure can make a big difference in how a system performs and feels. 

Most of my work revolves around taking complex ideas and turning them into solutions that are clear, reliable, and easy to work with. I enjoy building things that don’t just work but continue to work well as they grow.