Sentinel Pro App UX and Performance Architecture

>

App-Focused Technical Whitepaper (v4.3 Beta / v4.3b1-pro)

Date: 2026-04-01 Targets: iPhone, iPad, Apple TV

1. UX Design Intent

Sentinel app UX is designed to support two user modes:

• homeowner confidence mode (clear health, simple controls, trust visibility)
• integrator operations mode (high-density telemetry and controlled tooling)

Design principles:

1. Health-first hierarchy
2. Action guardrails before mutation
3. Progressive disclosure of advanced details
4. Performance-aware rendering for high-state homes
5. Role-appropriate affordances

2. Cross-Platform Layout Model

2.1 iPhone

• compact card stack
• quick-read health and incident blocks
• touch-priority controls
• modal detail sheets for service deep dives

2.2 iPad

• denser multi-column dashboard
• stronger at-a-glance operational matrix
• better side-by-side service and runtime summaries

2.3 Apple TV

• readability-first wallboard presentation
• focus-engine optimized interactions
• large target controls and stable remote navigation

3. Home Selection Architecture

Home selection supports:

• list and square layouts
• search by name/host/account type
• fast-open behavior with loading progress context

Core goals:

• minimize uncertainty while opening high-state homes
• preserve perceived responsiveness even during indexing

4. Dashboard Composition

The dashboard uses configurable widget composition with:

• baseline core widgets (health/tools/cloud/events)
• service-specific widget families
• role-aware visibility and action gating
• optional customization/edit mode

Widget classes include:

• system health and runtime
• cloud and incidents
• events and audit snapshots
• service rollups (lighting, shades, HVAC, AVB, security, entry, locks, etc.)
• tools and diagnostics

5. Performance Strategy in Large Homes

High-state homes can exceed several thousand harvested values. v4.3 beta app behavior addresses this through:

1. progressive render limits while data settles
2. staged loading overlays and status messaging
3. reduced animation cost in heavy states
4. caching and precomputation paths for widget data
5. large-home tolerant scrolling and lazy stacks/grids

6. Data Mapping and Service Agnosticism

Sentinel app parsing is designed to stay blueprint-agnostic by relying on:

• bridge catalog and discovery metadata
• path family heuristics and normalized service groupings
• resilient fallback strings for unknown/partial values

Mapping quality goals:

• meaningful status first
• avoid empty/ambiguous user-visible cards
• stable behavior when naming conventions vary by project

7. Connectivity and Session UX

Connectivity model:

• LAN and VPN supported
• bridge reachability reflected in dashboard status
• session-driven authorization updates shown in UI

Expected UX behavior when network changes:

1. detect unreachable bridge quickly
2. present clear offline/degraded status
3. avoid stale "connected" visuals after transport drops
4. support clean reconnect path without user confusion

8. Controlled Actions UX

For privileged actions, app UX should always enforce:

• explicit confirmation
• role and gate checks
• clear warning language
• post-action feedback and audit traceability

Examples:

• reboot requires confirmation semantics
• doorbell apply actions expose compatibility/update outcomes
• integrator access controls clearly distinguish temporary disable vs permanent

revoke impact

9. Doorbell Tool UX Considerations

Doorbell workflow quality targets:

1. fast sample list rendering
2. low-latency preview playback
3. explicit "apply" outcome state
4. clear operator message when service reload fails and reboot is recommended

Audio compatibility requirements are bridge-enforced and should be surfaced in plain language:

• codec
• sample rate
• channels
• bit depth
• frame duration

10. Apple TV Usability Requirements

tvOS interaction must maintain remote usability through:

• focusable controls for setup and home open paths
• large, high-contrast actionable targets
• deterministic focus movement in list/detail transitions
• no dead-focus surfaces in add-home and setup views

11. Accessibility and Readability

Recommended baseline:

• maintain strong foreground/background contrast
• avoid low-opacity small text for critical statuses
• ensure control hit areas remain generous on touch and remote targets
• provide concise but explicit error and warning text

12. QA Acceptance Criteria (App Layer)

12.1 Functional

1. Add home, edit home, and connect workflows function on all targets.
2. Dashboard widgets honor role and connection state.
3. Tools execute only when authorized.
4. Service cards display meaningful values where telemetry exists.

12.2 Performance

1. Home open action provides immediate loading feedback.
2. Scroll remains responsive after initial data hydration.
3. Widget edit/manage actions do not stall UI interaction.
4. Large-home rendering converges without freezing user controls.

12.3 Resilience

1. App gracefully handles bridge offline at launch.
2. VPN/LAN transitions trigger correct reconnect/offline signaling.
3. Session expiration and auth failures are recoverable without crash loops.

13. Future UX Hardening Priorities

1. Enhanced reconnect orchestration after network transitions.
2. More granular per-widget data quality diagnostics.
3. Expanded homeowner-safe explanations for advanced tool actions.
4. Additional tvOS focus telemetry and navigation test automation.

14. Conclusion

Sentinel Pro app architecture in v4.3 beta balances visual polish with operational depth. The direction is clear:

• powerful enough for integrator operations
• simple enough for homeowner trust and daily visibility
• performant enough for large Savant estates