Interactive worlds need more than visuals.

They need menus, tools, notifications, inventory systems, account flows, help panels, marketplaces, wallets, travel options, and project-specific interfaces that feel like they belong inside the experience.

That’s why GEM includes Deck Apps.

The GEM Deck is the in-scene player panel used for project apps, notifications, chat, authentication, and enabled bolt-ons. A helpful way to think about it is as a handheld tablet inside the scene — something a visitor can open, use, and put away without leaving the experience.

Instead of forcing every workflow into the host website, Deck Apps allow project tools to live directly inside the GEM runtime.

A Better Way to Add Project Tools

Every interactive experience is different.

One project may need an inventory system.
Another may need a wallet.
Another may need a marketplace, travel menu, onboarding guide, help center, or scene-specific control panel.

Deck Apps give projects a clean way to register custom HTML interfaces that can appear alongside built-in GEM tools.

That means project creators can add small, reusable interfaces without pulling the visitor out of the world.

The experience stays focused.
The tools stay available.
And the user remains inside the scene.

Built for Scene Context

Traditional website interfaces usually sit outside the experience.

They live in the page layout, separate from the world itself. That works for normal websites, but immersive environments often need something more connected.

Deck Apps are useful when the interface needs scene context.

For example, a player may want to:

• open an inventory while exploring,
• check a wallet balance inside the experience,
• buy or sell items in a marketplace,
• open a travel panel,
• follow an onboarding guide,
• view project-specific help,
• or use a custom tool tied to the current scene.

These are not just regular web pages.

They are tools that belong inside the runtime.

Browser Deck and VR Deck Support

Deck Apps can render inside the browser Deck, giving users a familiar panel-style interface while they interact with the scene.

They can also provide an optional VR Deck view for WebXR sessions.

That matters because immersive experiences may not always be viewed the same way. Some visitors may use a normal browser. Others may enter through VR. GEM’s Deck system is designed to support both paths while keeping project tools connected to the experience.

This makes Deck Apps a flexible foundation for browser-first and VR-ready workflows.

Perfect for Bolt-Ons

Deck Apps also work well for GEM bolt-ons.

A bolt-on may provide a specific feature, service, or system that needs a user-facing interface. Instead of building a disconnected page somewhere else, the bolt-on can appear inside the Deck beside other enabled apps.

This keeps the experience organized and gives users one place to access the tools available to them.

Examples include:

• marketplace tools,
• wallet interfaces,
• transit or travel systems,
• creator utilities,
• help panels,
• account-aware flows,
• and project-specific controls.

As GEM grows, Deck Apps create a consistent way for new tools to become part of the scene experience.

When Should You Use a Deck App?

Use a Deck App when the user needs to open a reusable interface while they are inside the scene.

Good examples include inventory, wallet, marketplace, travel menus, onboarding panels, project guides, account-aware flows, and small tools that need to stay connected to the GEM runtime.

Use normal page UI when the interface belongs to the host website instead of the scene experience.

That distinction is important.

Deck Apps are not meant to replace every page or dashboard. They are meant for tools that should feel native to the interactive world.

Keeping Users Inside the Experience

One of the goals behind GEM is reducing friction.

If a visitor has to constantly leave the scene to manage inventory, read instructions, sign in, open a marketplace, or access a project tool, the experience starts to feel fragmented.

Deck Apps help solve that.

They keep useful interfaces close to the user without breaking immersion.

Open the Deck.
Use the tool.
Put it away.
Keep exploring.

That simple pattern makes interactive experiences feel more complete and more natural.

Building Beyond the Page

Deck Apps are another step toward GEM’s larger vision: building web experiences that feel less like static pages and more like living systems.

As projects become more interactive, the tools around them need to become more interactive too.

Deck Apps give creators and developers a way to bring project-specific workflows directly into the runtime, whether that means inventory, commerce, travel, onboarding, support, or something entirely custom.

The web experience stays connected.

The scene stays active.

And the tools become part of the world.

You can learn more in the Deck Apps documentation:
https://gem4d.com/documentation/javascript-api/deck-apps