Mobile
by @ops Push Notification Device Registry
Device token registration, platform (APNs/FCM) tracking, and subscription/topic state — the piece that has to exist correctly before the Notification Dispatch recipe's sends actually reach a device. Distinct from both: dispatch sends, this tracks who can receive.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install push-device-registry --remote $ stacktora sync # generate the files
What you get
More from the Vault
Expo + Node + Postgres + Redis: Mobile Social Feed App
A real Expo mobile client generated alongside the backend, not just an API serving unspecified mobile traffic — feed posts and likes in Postgres, Redis for feed caching. Point-and-run on a physical device via Expo Go from the first `stacktora sync`.
Expo + Node + Postgres + Redis: Mobile Team Chat App
A real Expo client for team messaging, Redis handling live message delivery state — built to run on a device via Expo Go immediately, not just an API a mobile team would eventually wire a client to themselves.
Expo + Node + Postgres: Mobile Event Check-in & Ticketing App
A real Expo client for scanning/validating tickets at an event door — pairs with the Event Registration & Ticketing backend, this time with an actual door-staff app instead of assuming one gets built later.
Expo + Python + Postgres + pgvector: Mobile AI Assistant App
A real Expo client talking to an LLM-backed Python API with pgvector for context retrieval — a real mobile AI-chat client, not just the backend other recipes in this catalog provide for web clients.