💡 Expo Home Screen Widget for Live Market Status

[github-actions[bot]]

Summary

Use Expo's new Widgets API (alpha in SDK 55) to display live market-day status directly on the customer's home screen — vendor count checked in, next market time, and followed vendor alerts — without opening the app. This creates a passive, always-visible engagement surface that reinforces the confidence-first positioning and differentiates Markets from every competitor in the space.

Market Signal

Expo SDK 55 (Feb 2026) introduced Expo Widgets (alpha) supporting iOS home screen widgets and Live Activities. No competing farmers market app offers home screen widgets — LocalHarvest is web-only, Farmish has no mobile-native innovation, and market management tools (ManageMyMarket, Marketspread) don't have consumer-facing mobile apps. Apple's continued emphasis on widgets and Live Activities as primary engagement surfaces means customers increasingly expect glanceable information without app launches. Source: Expo SDK 55 Changelog.

User Signal

Rachel (customer persona) plans her Saturday morning around market confidence. Currently she must open the app to check vendor status. A home screen widget showing "12 of 18 vendors checked in at Riverside Market" or "Green Valley Farm just checked in" delivers the confidence signal passively. The PRD's 60-second propagation SLO (NFR2) ensures widget data stays fresh. This aligns with the PRD's core metric: customer confidence that translates into trips taken and completed.

Technical Opportunity

Expo Widgets is built on the Expo Modules API and supports both static and timeline-based widgets. The existing Firebase Realtime Database architecture (paths: /markets/{marketId}/vendors/{vendorId}/status) provides the real-time data source. Widget updates can be triggered by background push notifications via FCM, which is already in the planned stack (Epic 7). The widget would read from MMKV (already planned for offline cache), keeping the widget process lightweight. iOS Live Activities could show real-time check-in progress during market hours — a natural extension of the widget concept.

Assessment

Dimension	Score	Rationale
Feasibility	med	Expo Widgets is alpha; needs to mature through 1-2 SDK releases before production use
Impact	high	Unique differentiator — no competitor offers this; directly serves confidence-first positioning
Urgency	med	Post-MVP feature; timing aligns with Epic 6 (Customer Discovery) development

Adversarial Review

Strongest objection: Expo Widgets is in alpha — shipping production features on alpha APIs risks breaking changes, platform instability, and App Store rejection. The Markets app has no codebase yet; adding experimental features before core functionality exists is premature optimization.

Rebuttal: The proposal is timed for post-MVP development, not Sprint 1. By the time Markets reaches the customer discovery epic (Epic 6), Expo Widgets will have matured through several SDK releases. The widget is a read-only view of existing data — it adds no new backend complexity and is architecturally decoupled. Even if the API changes, the widget is a thin UI layer that can be updated without touching core logic. Starting the design work now (data model, update triggers) ensures the architecture supports widgets from day one.

Suggested Next Step

Track Expo Widgets API stability through SDK 56-57 releases; create a proof-of-concept widget showing static market data once Epic 6 customer discovery is underway. Design the MMKV data contract that both the main app and widget process will share.