💡 Apple/Google Wallet Market Pass for Passive Retention

[github-actions[bot]]

Summary

When a customer follows a market, they receive a digital pass for Apple Wallet or Google Wallet. The pass shows the next market date, location, and count of followed vendors. It auto-updates each week and delivers lock-screen notifications when followed vendors check in — without requiring the customer to open the app. This creates a zero-effort passive retention channel.

Market Signal

Wallet passes achieve 70%+ retention vs app push notifications which get disabled by 40%+ of users. VeeCard and PassKit demonstrate wallet-based engagement at scale. Digital loyalty cards using Apple/Google Wallet are a growing trend across retail (Stamp Me, Loopy Loyalty, PassKit all expanding in 2026). No farmers market app currently offers wallet-based market passes, representing a clear differentiator in the local food space.

User Signal

The Digital Market Visit Rewards idea (#363) addresses loyalty via reward points, but wallet passes solve a different problem: passive engagement and information delivery without app friction. Customers who follow markets need a zero-friction way to remember market days and see live status — the wallet pass sits on their lock screen alongside boarding passes and event tickets, appearing at exactly the right moment.

Technical Opportunity

PassKit.js (Apple) and Google Wallet API are well-documented with community Expo packages available. The pass template is simple: market name, next date, location, vendor count. Pass updates can be pushed server-side when market or vendor data changes. The existing Firebase Realtime infrastructure can trigger pass updates when followed vendors check in. The Go backend can generate and serve pass files via a dedicated endpoint.

Assessment

Dimension	Score	Rationale
Feasibility	high	Apple Wallet pass generation is well-documented; pass template is simple; server-side push updates are straightforward
Impact	med	Creates a passive retention channel that reaches users who disable or ignore app notifications; differentiates from all competitors
Urgency	low	Best value after the follow relationship is established and active — a Phase 2 retention feature

Adversarial Review

Strongest objection: Google Wallet coverage is only ~70% of Android phones. Building and maintaining two separate pass platforms (Apple + Google) doubles integration work.

Rebuttal: Start with Apple Wallet only (near-universal iOS coverage) and add Google Wallet as a fast follow. The pass template is simple enough that dual-platform maintenance is minimal. For Android users without Google Wallet, the feature simply isn't available — graceful degradation. The ROI on iOS-first is strong given the customer demographic (health-conscious local-food shoppers skew iOS).

Suggested Next Step

Prototype an Apple Wallet pass template showing market name, next date, location, and vendor count. Test server-side pass updates via APNs push. Evaluate expo-passkit community packages for React Native integration.