Business App navigation and push boundaries

Treat navigation as an application-owned contract. Integrations may provide a supported business intent and validated data, but they must not depend on internal screen names, navigator nesting, or component symbols. Those details can change without becoming a public compatibility promise.

Before you start

• Use a build whose Business App, Ordering Components, and environment relationship are known.
• Use synthetic order and account data. A push test may register a device token or contact an external provider and is not a read-only action.
• Confirm the authenticated user can access the referenced business and order through the API before testing a navigation handoff.
• Define the expected fallback when the app is signed out, still loading, or cannot resolve the destination.

Scope and version

Authority	Supported public boundary	Version or pin limitation
Business App	Owns registered root, authenticated, and tab navigation; it decides when a supported intent can be opened.	The registered graph is source-version-specific and is not a stable route-name API.
Ordering Components	Supplies session, order, configuration, and realtime state used by navigation decisions.	The app consumes an exact Components revision; other revisions require a new compatibility review.
Ordering API	Authorizes the referenced resource and accepts eligible notification-token registrations.	Current source was traced, but deployment equivalence is unknown.
Push provider and operating system	Deliver notifications and report device subscription state.	Delivery, permission prompts, background behavior, and tap handling vary by provider, platform, build, and device state.

Inputs and configuration

Input or configuration	Owner	Validation and availability	Failure boundary
Navigation intent	Business App	Must map to a currently supported app outcome after the app is ready.	An internal destination identifier is implementation detail and must not be sent as an integration contract.
Resource reference	Integration producer and Ordering API	Must identify an authorized resource in the selected project without exposing sensitive data in logs or links.	A well-formed reference does not prove that the signed-in user can read it.
Authenticated and loaded state	Business App and Ordering Components	The app waits for session, configuration, and required order state before attempting a handoff.	A handoff received too early may be deferred, ignored, or require the operator to open the item manually.
Push application and device subscription	Deployment owner, push provider, and operating system	Provider configuration, permission, subscription state, user identity, and project must align.	Token creation, API registration, provider delivery, and tap handling can fail independently.
Inbound URL	Integration producer	No general inbound app-link or universal-link contract is established by the reviewed source.	Do not assume a web URL or custom scheme will open an internal Business App destination.

Lifecycle and outputs

For ordinary in-app navigation, the Business App selects a root workspace from loading and authentication state, then presents the authenticated workspace and its registered child destinations. Tabs and child pages remain internal composition details.

For a push handoff:

1. The provider reports a notification interaction to the app.
2. The app extracts only the supported resource intent from the payload.
3. The app waits for authentication and required application state.
4. The app attempts to open the corresponding authenticated outcome.
5. The API remains responsible for authorizing and returning the referenced resource. Provider delivery never bypasses API authorization.

The reviewed source shows an intended push-to-order handoff, but no accepted runtime receipt correlates that handoff with a deployed binary, provider, and API environment. Treat it as source-intended behavior and provide a manual fallback until that scenario is independently verified.

Platform and provider limits

• Push permission, token creation, notification delivery, foreground/background behavior, and notification taps are separate checkpoints.
• Registering a notification token is a server write. Run it only in an approved synthetic environment with cleanup and independent review.
• The app’s internal navigator graph can be nested. An integration must express the outcome it needs, not attempt to traverse that graph itself.
• The reviewed mobile manifests do not establish general inbound deep linking. Outbound links to another app or website are a different responsibility and do not imply an inbound navigation contract.
• Realtime events and push notifications are separate transports. Receiving one does not prove the other is configured or current.

Troubleshooting and escalation

Observable behavior	Owning boundary	Next action
A notification is not shown.	Operating system or push provider	Check permission, subscription, provider environment, and payload delivery before debugging navigation.
A notification is shown but the app does not open the expected order.	Business App handoff	Confirm the app was authenticated and fully loaded, then use the in-app order search as the safe fallback. Escalate with build and synthetic scenario details.
The app opens but the resource is unavailable.	Ordering API authorization or data state	Confirm the selected project, signed-in user scope, and current resource state. Do not retry with a different user’s identifier.
A URL opens the browser instead of the app.	Inbound-link boundary	This source version does not establish a general inbound link contract. Direct the operator to open the Business App and find the item in-app.
Behavior changes after a Components or app update.	Release owner	Revalidate the registered graph and push handoff against the exact paired revisions before treating the change as supported.

Related articles

• Business App architecture and configuration
• Business App overview

:::note Visual status Visual guidance is deferred. Navigation or push diagrams require a separate authorized and reviewed visual program. :::