Admin Extensions / API 2026-07

Build App Home as a "UI extension"
An app landing page with no dedicated web server required

New admin.app.home.render target lets you build your app's landing page (App Home) as a Preact-based admin UI extension. It ships in the same bundle as your other admin UI extensions, so you no longer need a separate web server to render App Home.

On this page
  1. What's actually changing (understand it in 30 seconds)
  2. How it works: the difference from the traditional iframe approach
  3. When to use this extension type
  4. Availability (supported / not supported)
  5. Getting started (command steps)
  6. 5 key points for developers
  7. 3 use cases you can apply to your work
  8. A one-line summary you can use in a pitch

1What's actually changing

The first thing shown when you open an app App Home (the app's landing page) was, until now, rendered by hosting it in an iframe on your own web server.
This time, the admin.app.home.render target was added, so you can now build App Home as a Preact-based admin UI extension. Because it ships in the same bundle as your other admin UI extensions,no separate web server is needed to render App Home.
iframe + your own server

Before: iframe hosting approach

App Home was provided as a separate web app and embedded in the Admin via an iframe. Running and hosting a server was required just for the landing page.

New: UI extension approach

admin.app.home.render describes App Home as a UI extension. It ships alongside your other admin extensions, giving you the performance and design benefits of Polaris web components without a server.

2How it works: the difference from the traditional iframe approach

Before: iframe hosting approach Shopify Admin Display App Home iframe Your own web server Hosting and operation required Other UI extensions Managed in a separate bundle New: UI extension approach (admin.app.home.render) Shopify Admin Display App Home A single extension bundle App Home block extension action extension No server required
App Home = the "main workspace (cover page) of the app" that appears first when you open the app. In the new approach, this is distributed in the same bundle as other admin UI extensions, sothe "single source of truth" for the app's main UI is consolidated in one place.

3When you should use this extension type

The three conditions the article lists for "when you want to use this extension type."

A permanent, full-screen workspace

When, instead of a web app hosted in a separate iframe,a permanent full-page workspace integrated into the extension bundleis what you want.

Unify the source of truth for the main UI

When you want to manage the app's main UIas a single source of truth alongside other admin UI extensionsthe way you'd manage them.

The benefits of Polaris without a server

When, without hosting a web server for App Home,the performance and design-system benefits of Polaris web componentsare what you want.

4Availability (in scope / out of scope)

ItemDetails
Supported API version 2026-07 and later The App Home UI extension is available from this version
Intended app type Custom-distribution apps For custom-distribution apps
Public apps (App Store) Out of scope Public apps for the Shopify App Store should continue to use the iframe-based App Home instead
If you're developing a public app (distributed via the App Store), it's explicitly stated to continue using the traditional iframe-based App Homerather than this UI extension approach. The new approach is strictly for custom-distribution apps.

5Getting started (command steps)

1

Pattern A: Start with a new app

Scaffold an extension-only app. In the prompt, "Build an extension-only app" select.

2

Pattern B: Add to an existing app

To add an App Home UI extension to an existing app, in the prompt, "App home" select.

3

Check the reference

For the full list of target APIs, web components, and configuration options, see App Home UI extension reference for details.

Pattern A: Scaffold a new extension-only app

$ shopify app init # In the prompt, select "Build an extension-only app"

Pattern B: Add an App Home extension to an existing app

$ shopify app generate extension # In the prompt, select "App home"
The rendering entry point is the admin.app.home.render target. Detailed APIs, available web components, and configuration options are all consolidated in the official App Home UI extension reference.

6Five key points engineers should know

Preact

1. A Preact-based UI extension

An admin UI extension built on Preact that renders App Home at the admin.app.home.render target. You no longer need to maintain the frontend as a standalone web app inside an iframe.

2. No more web server operations

You no longer need a separate web server just to render App Home. For the landing page, the operational burden of hosting, scaling, and monitoring is eliminated entirely.

3. Bundled with other admin extensions

App Home goes into the same bundle as other admin UI extensions such as block and action. Deployment and versioning are unified at the extension-bundle level.

4. Built on Polaris web components

You get the performance and design-system benefits of Polaris web components without server hosting. It's straightforward to build a UI consistent with the admin.

2026-07

5. Scope: custom distribution apps + API 2026-07

Available for API version 2026-07 and later, and custom distribution apps.Public App Store apps continue to use the iframe-based App Home. Adoption depends on the distribution model, so determine the project type first before starting design.

7Three use cases you can apply to your work

USE CASE 1

Make the admin UI serverless for internal / client-only apps

Challenge
For a custom distribution app built for a specific company, you keep running a web server just for the landing page and maintaining its hosting, SSL, and scaling.
Solution
App Home admin.app.home.render Migrate to a UI extension and bundle it alongside the other admin extensions.
Impact
Eliminates the operational overhead and cost of running a server for the home page. Reduces the maintenance surface while keeping a Polaris UI consistent with Admin.
Technical notes
Requires API 2026-07 or later.shopify app generate extension It can be added to an existing app via "App home."
App Home block extension action extension
USE CASE 2

Consolidating an extension-heavy in-house tool into a single bundle

Problem
An in-house tool with multiple admin UI extensions such as block and action keeps only the home page in a separate repo and separate deployment, so the source of truth for the UI is fragmented.
Solution
Turn App Home into a UI extension and consolidate it into the same bundle as the existing admin extensions, unifying the single source of truth for the main UI.
Impact
Deployment and versioning are aligned at the extension-bundle level, simplifying UI consistency and release management.
Technical notes
The article makes clear that it is "a single source of truth that sits alongside the other admin UI extensions." CI can also be consolidated around building/deploying the extension bundle.
$ shopify app init > extension-only
USE CASE 3

Templatizing custom app launches for agency development

Problem
An agency mass-produces custom-distribution apps per client, but each launch is heavy because it rebuilds the App Home server setup from scratch every time.
Solution
shopify app init Use "Build an extension-only app" to scaffold an extension-only app and standardize an internal template that handles everything up to App Home as an extension.
Impact
An initial setup that includes the home page can be spun up without a server, cutting per-project initial effort and infrastructure procurement.
Technical notes
Projects intended for App Store release are out of scope (they continue with the iframe-based approach). It fits well when custom distribution is the primary model for agency work.

8One-line summary for pitches

"A new approach that lets you build an app's home page (App Home) as a admin.app.home.render Preact-based UI extension.
No dedicated web server needed, bundled with the other admin extensions, and keeps all the benefits of Polaris.
It targets custom-distribution apps on API 2026-07 or later (App Store apps continue with the iframe approach)."