One Product, One App

One Stardeck app is usually one product. You build it once. Your customers and staff use many experiences inside it.

​

The building blocks

​

One app, many experiences

Modules supply reusable capabilities to the app. Surfaces present those capabilities as focused experiences for different audiences and devices. They still share one product boundary and ship together. Different audiences or devices alone do not mean you need another Stardeck app. Customer ordering, counter POS, kitchen display, and back office can live as Surfaces of one restaurant system. Marketing site, customer portal, and staff admin can live as Surfaces of one booking product. Create a separate app only when you need a genuinely independent product, tenant boundary, owner, data model, or release cadence. See When to Create a Separate App.

​

How to decide

Blank creation is available to everyone. Organizations with Alpha access may instead choose Start from a Blueprint or Start from Modules — those two choices are mutually exclusive.

​

Examples

​

Restaurant operations

One restaurant system app can include:

• Surfaces: customer ordering, POS, kitchen display, back office
• Modules (Alpha, optional): orders, catalog, payments, loyalty

Staff and customers each get their own launchable experience. You still publish the product once. Walk through it in Restaurant Surfaces.

​

Service business

One booking app can include:

• Surfaces: marketing site, customer portal, staff admin
• Modules (Alpha, optional): booking, payments, notifications

Public and internal experiences share one product without sharing the same access rules.

​

Learn each piece