Mobile
by @ops Node + Postgres + Redis: Mobile App Version Gating & Force-Update Backend
Minimum supported app version checks and force-update logic — distinct from Push Device Registry and Mobile BaaS: this is specifically the 'your app version is too old, please update' gate every mobile team eventually needs and usually builds ad hoc.
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 node-mobile-version-gating --remote $ stacktora sync # generate the files
What you get
More from the Vault
Geofencing & Location Tracking Backend
Location updates, geofence definitions, and enter/exit event detection in Postgres, with Redis for the last-known-position lookups that need to be fast. The backend shape behind delivery tracking, ride-hailing, or any location-aware mobile feature.
Mobile Backend-as-a-Service
Postgres + Redis backend shaped for mobile clients specifically: auth, sync-friendly data access, and Redis ready for push-notification queuing. A real starting point instead of reaching for a generic web API stack and bolting mobile concerns on after.
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.
Python + Expo + Postgres + Redis: Mobile App Backend
A backend built specifically for a mobile app: Python API paired with a real Expo (React Native) app scaffold, Postgres for user/app data, and Redis for sessions, push-token caching, and rate limiting.