Business App developer reference
Build and maintain operator workflows without treating internal routes, client configuration, or native-provider behavior as a public API. Start with the product experience, then use the integration contract or engineering guide that owns your change.
Product workflows
- Business App product guide — understand the operator experience for orders, fulfillment, businesses, messages, account access, payments, and printing.
Product documentation describes observable outcomes and current limitations. It does not grant access to source repositories, configuration, customer data, or a live environment.
Integrations
- Navigation and push boundaries — preserve application-owned navigation and separate provider delivery from authorized resource access.
- Native integration safety boundaries — assign responsibility for permissions, realtime, files, maps, external apps, clipboard, PDF, printers, audio, and vibration.
Use synthetic data and an approved isolated environment for any integration test that can register a device, open another app, publish an event, create a file, or produce physical output.
Engineering
- Business App engineering guide — set up the repository, understand its layers, run the native apps, verify changes, and prepare a release handoff.
- Architecture and configuration — understand the responsibility boundaries among the native shell, Ordering.co Components, the Ordering.co API, runtime configuration, and external providers.
Available capabilities depend on the app build and API revision enabled for the target deployment.