Check Signage before rollout

Separate the current overview implementation from the complete device-mode design.

Before you begin

  • Record the actual installed app version and source revision.
  • Use authorised test bookings and credentials, not live visitor data.
  • Plan physical door tests with the site’s access operator.

Source review: feature/digital-signage-ads-co at bd1a6cd (overview app) and qat at 07f9041 (place/schedule data), reviewed 8 September 2026. This site update changes marketing and help only; it does not implement or certify the device app.

Step by step

  1. Confirm the overview baseline

    The reviewed app has a portrait shell, floor rotation and pinning, floor-plan/room-grid composition, status badges, booking-page QR, OAuth/session plumbing and live resources, resource_kinds, bookings and booking_lines. It also has mock, ads and offline paths. Test the real connection; a sample screen is not acceptance.

  2. Verify first-boot setup and restart

    The reviewed parser uses URL/build configuration rather than the required saved wizard. Confirm credentials → mode and resource/floor → locked orientation → Overview content switches → save. Restart, confirm setup is skipped, then verify the approved hidden gesture/PIN reopening route.

  3. Verify real places and session data

    The reviewed overview synthesises floors from resource kinds and reads booking.username for the booker. Connect real signage_places, the combined signage_schedules day view, attendee/gym identities and event join links. Validate that all information belongs to the bound project and resource.

  4. Test the door and in-room modes separately

    Access must use one resource, personal visitor BookingAccess, member Hik face and booking-window-gated open/deny. In-room must show this session’s people and timing, verified service actions and an event-link join action. Gym rules require the current one-hour slot, at most five employee first/last names and no company or visitor data. These are target integrations, not working modes in the reviewed overview branch.

  5. Test orientation, panes and exclusions

    Confirm portrait and landscape stay locked after resize and restart. Test both panes, plan only, rooms only and ads-only. Verify a fitted 16:9 top video in portrait and fitted 9:16 left video in landscape. Access has no map/join/ads; In-room has no lock/visitor QR/ads. Graph write-back remains outside Signage.

You’re ready when

Each target behavior has been demonstrated on the installed build, and incomplete areas are recorded before rollout.

Troubleshooting

A marketing concept is being used as proof
Use an actual installed-build test instead. The product images and on-page layout explorer are labelled concept previews.
An acceptance check fails
Record the failing mode, resource, time and source revision, remove any private credentials from evidence, and have the implementation corrected before depending on that function.

Common questions

Did this website update implement the device wizard or lock control?
No. It updates the Spaze Signage product story and Help Center to the requested contract, with the current code baseline and validation work made explicit.
Can the old overview be certified as all three modes?
No. Rotation, room cards and a booking QR do not establish Access or In-room behavior.
Is Graph write-back part of Signage acceptance?
No. Keep Graph write-back as a separate booking-side task. Ingested calendar data and joining an existing event link are different responsibilities.

Still stuck? Tell support what happened and which step you reached.

Email support