Architecture
What Is An App
The canonical definition of an app in Saas Dash and the platform registry
Decision
An app is a top-level business surface, not a deployment artifact.
In this platform, an app should be:
- independently understandable by an operator
- independently assignable to a tenant or plan
- independently visible in top-level navigation
- independently described in the app registry
If a surface does not meet that bar, it should not become a top-level app.
What is not an app
These are not apps by default:
- products
- categories
- orders
- fulfillment
- payment methods
- shipping methods
- tax engines
Those are usually modules, extensions, or shared services.
Why the platform differs from mobile
On mobile, the operating system forces the app boundary to be the binary.
This platform is not constrained that way.
That means the app boundary should be chosen around:
- business workflow
- operator mental model
- entitlement simplicity
- navigation clarity
The correct unit is the product surface, not the package shape.
Current examples
Good top-level apps:
shopgivingcrmbookingsmembershipswhen access/community workflow becomes its own business surface
Bad top-level app candidates:
shop-productsshop-ordersshop-categoriespayments
Those create artificial catalog noise and make plan management worse.