HSLG Media

App Demo Runtime

App Demo Runtime module

Runs the same customer UI with explicit fictional responses only inside the WordPress showcase.

How the presenter starts and where fiction enters

StartDemo.js initializes the browser-only shared application. DemoServices.js supplies explicit fictional data and outcomes so an owner can review interactions without activating external billing, reservation or account providers. PhonePreview.js and PresenterOverlays.js handle presentation-specific framing, controls and example interactions. These modules are not intended for an Android customer bundle.

Actual boundaries

A successful simulated order in this runtime is evidence that a screen and its callbacks can be displayed; it is not evidence that an API request, payment or kitchen message happened. The demo data and phone chrome are excluded from the native service and asset graph. When a shared UI capability changes, update the demo implementation to demonstrate both success and relevant failure paths without introducing a switch that could enable fiction in a production build.

Verification

Use the Chromium browser journeys for all five venues, table ordering, QR/offline links, login and negative scenarios. Check responsive sizes and presenter controls independently of the mobile APK. A visual defect in shared screen code should be fixed in packages/app-ui, not patched a second time only in a WordPress presenter file.

Source files in this module

Maintenance and evidence

Check all affected file references and the matching human-readable user/architecture page when source changes. Run the module’s contract or governance checks; staging, payment and native hardware tests remain independent of source inventory coverage.