DisplaySync

Mobile app

The DisplaySync mobile app lives on the AV tech's phone, not on the event manager's laptop. It's the right tool when you're standing in front of a sign with hands full of cables — claim, reboot, send a log bundle, move on.

For anything you'd do at a desk (planning the event, building the run-of-show, managing org members), use the web dashboard instead.

(New to DisplaySync? Walk through Claim your first sign before continuing — it covers the end-to-end loop from install to a live wall.)

Where to get it

PlatformDistribution
iOSTestFlight — invite link from the engineering team
AndroidGoogle Play internal testing — opt-in link from the engineering team

The same login works across both platforms and the web dashboard.

What's on the screen — two tabs

The mobile app uses an event-first navigation model. The bottom tab bar has two tabs in V1:

TabPurpose
Events (default)The event list; tap an event to open its per-event hub. The "current event" persists across app launches.
ProfileAccount, push notification settings, organization switcher, sign-out.

The header has a notification bell (top-right) that opens the in-app feed — there is no separate Notifications tab. Push and email channels configure under Profile → Notifications.

Sign-in uses email/password or Google Sign-In (native Google SDK on both platforms).

EventDetailScreen — the per-event hub

Tapping an event in the Events tab opens its detail screen — the home base for everything you do at a show. Three surfaces matter day-of:

  • Filtered Signs list. The signs in this event, with health-status filter chips at the top (online / offline / all). Each row shows name, location, status indicator, and last-heartbeat time. Tap a row to open the sign detail screen.
  • FAB bottom-right labeled "Add a sign to this event" (QR-code-scan icon). Tap to open the scanner — this is the entry point for both claiming a new sign and linking to a pre-created one.
  • Kebab menu (top-right, next to the bell). Three options: Pre-register a sign (Flow B record creation), Group by Location toggle, Team (per-event role management for org owners/admins/managers).

Daily workflows

The five workflows you'll run from a phone at a venue:

1. Claim a new sign

  1. Events tab → tap the event you're working in.
  2. Tap the bottom-right FAB ("Add a sign to this event").
  3. Scan the QR code on the kiosk's screen. (If the QR is unscannable, tap the manual-entry link and type the 6-character short code.)
  4. Fill in Name and optional Location.
  5. Claim — the kiosk transitions out of QR mode within 1 second.

Full detail and edge cases: Claiming signs → Flow A.

When the event manager pre-built Sign records in the dashboard, the same scan path routes you to the link flow instead of the claim flow:

  1. Events tab → tap the event → FAB → scan the kiosk's QR.
  2. If the kiosk's signId is already on an unlinked Sign record in this event, the scanner routes to the Link screen instead of the claim screen.
  3. Confirm — the existing record's device fields populate. Name, location, and content stay as the manager set them.

The physical path is the same (Events → event → FAB → scan); the app routes by what it finds in the dashboard, not by which button you press.

3. Walk the floor: verify everyone's healthy

The EventDetailScreen's filtered Signs list is the floor-walking surface:

  • Pull-to-refresh forces a sync (otherwise updates land via push).
  • Filter chips at the top let you see only Offline signs — the ones that need attention.
  • Tap a sign row to open the sign detail screen with status, network, commands, and recent activity.

A common rhythm: filter to Offline, walk to each one in venue-order, triage on the spot.

4. Trigger remote actions

The sign detail screen has the same remote-control buttons the dashboard does, organized in a row:

  • Refresh — reload the assigned URL
  • Reboot app — exit and relaunch the sign app (~60 s)
  • Reboot device — full Windows restart (~90 s)
  • Fetch logs — pulls the latest log and opens a viewer

The sign detail screen does not let you edit the assigned content URL — that's a dashboard-only action. See What the mobile app does not do below.

5. Pre-register a sign

For events where the manager is building the Sign records in advance (Flow B):

  1. Events tab → tap the event → kebab menu (top-right)Pre-register.
  2. Fill in the Sign record's name, location, optional notes.
  3. The record appears in the event's Signs list as Unlinked until a kiosk scans into it via the link flow (workflow 2 above).

Sign detail screen

Tapping any sign row in the EventDetailScreen list opens the sign detail screen. Sections:

  • Status — current state (online/offline/error/maintenance/unlinked), connected duration
  • Network — IP, Tailscale IP, active interface
  • Commands — Refresh, Reboot app, Reboot device, Fetch logs
  • Recent activity — the same Event log entries that appear on the dashboard

See Remote control for the dashboard-side equivalent and what each command does on the kiosk.

Notifications and badging

The app registers for push notifications on first launch (you'll be prompted). The header bell badges with the count of unread items; tap to open the in-app feed.

Notification types include sign offline / online, content unreachable / recovered, and event team-membership changes. Each item deep-links to the relevant sign or event.

See Notifications for the full channel and subscription model.

Permissions

The app requests three OS-level permissions:

PermissionWhy
CameraScanning QR codes
NotificationsPush alerts for sign state changes
Local network (iOS only)Kiosk discovery on the same LAN (optional, only used as a fallback if a sign's QR is missing)

You can decline any of these — the corresponding feature won't work, but the rest of the app does.

Your event role determines which buttons appear on the sign detail screen. Viewers see read-only; technicians can run commands and edit kiosk-side fields; managers can also edit event metadata and the team. See Roles & permissions.

Working offline

The mobile app isn't useful without network — all the workflows depend on talking to the backend. But it does fail gracefully:

  • Recent data (events, signs) stays cached and viewable.
  • Actions (claim, remote command) queue and retry on reconnect.
  • A persistent banner shows "Offline" so you know what you're looking at.

If you're working in a venue dead zone, hop onto the venue Wi-Fi (or pre-stage your phone on the same network the kiosks are on) before doing anything destructive.

Sign-out and switching orgs

  • Profile tab → Sign out clears the local session (push tokens are revoked).
  • If you belong to multiple orgs, Profile → Switch organization lets you switch. The current event resets when switching.

What the mobile app does not do

Some things deliberately live on the web only:

  • Content URL editing — assigning or changing a sign's URL is a dashboard-only action
  • Event creation — events are created on the web, then techs operate them from mobile
  • Org-level admin — billing, team management at the org level, invitations, settings

If you find yourself wanting to do any of these from mobile, jump to the dashboard for that step. The accounts are the same.

What's next