The same CRM, in your pocket — even with no signal.
A native iOS and Android app with an offline-first local cache, business-card scanning, delta sync, push notifications and biometric login — a first-class client of the same /v1 API and the same login as the web app, currently in private beta.
GENECRM's mobile app isn't a stripped-down companion — it's built against the same backend contract as the web app (the /v1 API, the same tenant and RBAC model) with a local, offline-capable data layer on top. Contacts, leads, opportunities, tasks and activities are cached on-device and kept in sync with the server via a cursor-based delta-sync endpoint, so the app is usable in the field with poor or no connectivity and catches up automatically the moment it's back online. In the field you can also scan a business card with the phone's camera: on-device text recognition reads the name, company, email and phone straight into a new contact you review before saving. The app is in private beta ahead of its App Store and Google Play release — talk to us about getting your team a build. Mobile is a paid feature, entitled on the Premium, Pro and Enterprise plans.
Offline-first local cache
The app stores contacts, leads, opportunities, tasks and activities in an on-device database that mirrors the server's sync entities, so lists, search and record detail all work without a network connection — reads never block on the server.
Delta sync
A single endpoint (GET /v1/mobile/sync) returns everything that changed since an opaque cursor, per entity, tenant-scoped by row-level security. The cursor encodes (updated_at, id) so paging is stable even when many rows share a timestamp — no gaps, no duplicates.
- Omit the cursor for a full backfill on first login or a fresh install
- has_more=true means more changes are waiting; the client repeats the request with the new cursor until it's false
- entities= lets the client choose which of contacts/leads/opportunities/tasks/activities to sync, and fields= projects down to just the columns it needs
- Up to 2,000 changed rows per entity per request (default 500)
Push notifications
The app registers its APNs/FCM push token via POST /v1/devices (upserted per device, re-homed to whoever is currently logged in); a background push worker fans out queued notifications to every device a user has registered, retrying failed deliveries up to 5 times before giving up.
Biometric login
After the initial email/password sign-in, the app can unlock with Face ID / Touch ID (iOS) or fingerprint/face unlock (Android) instead of re-entering a password, falling back to device passcode when biometrics aren't available or enrolled.
Same login, same backend, real session security
Mobile authenticates against the same tenant and user accounts as the web app via a password-grant token endpoint, returning a short-lived 15-minute access token and a 30-day rotating refresh token (only its hash is stored server-side). Refresh tokens rotate on every use — reusing a revoked token is an automatic 401 — and login is rate-limited to 20 attempts per 5 minutes per IP.
- Field sales reps updating opportunities and logging activities with no reliable signal
- Account managers checking in on a contact or task from their phone between meetings
- Teams that want mobile push reminders for tasks and CRM notifications
- Anyone who wants to unlock the app with Face ID instead of typing a password every time
Mobile app — common questions
Yes — contacts, leads, opportunities, tasks and activities are cached on-device, so browsing and searching work offline. Changes sync automatically the next time the app has connectivity.
No — mobile is a paid feature included on the Premium, Pro and Enterprise plans. Tenants without it receive a 402 Payment Required when attempting to sign in from the app.
No — the app uses the same email and password (and the same tenant/user account) as the web app. It gets its own short-lived access token and rotating refresh token so a lost phone can be revoked without affecting your web session.
The first sync is a full backfill of every record the tenant's RLS policy allows the user to see; after that, only changes since the last sync cursor are fetched, so subsequent syncs are fast and small.
Yes — once a device registers its push token, CRM notifications (new leads assigned, task reminders, etc.) are delivered to every device you're logged in on via APNs (iOS) or FCM (Android).