Mobile vs Web — What's Different
Quick reference for what's mobile-only, what's web-only, and what works in both places. Helps you know which device to grab for a given task.
Steps
- Mobile-only (hardware features the desktop can't do): NFC tap-to-share, Camera capture in Meet Mode, Voice memo + AI transcription in Meet Mode, GPS trip tracking, push notifications, haptic feedback.
- Web-only (admin / content creation surfaces that don't fit on a phone): Web Studio site + funnel builder, the visual workflow editor canvas, the AI Actions audit log, finance proposal editor, the full analytics report builder, super-admin panel, brokerage slot management UI, integration setup (Stripe, Twilio, Meta, etc.), all suite-toggling under Settings > Billing.
- Both web + mobile: Contacts, Calendar, Pipeline, Inbox, Comm Pro chat, Real Estate listings, Client Hub document view, Settings (per-user prefs), Notifications.
- Same data store either way — sign into mobile and the changes you made on web are already there (no per-device sync to manage).
Good to know
- Authentication: same JWT login, no separate mobile account. If your account is suspended on web, mobile is suspended too.
- No biometric (FaceID / TouchID) login yet — you log in with email + password and stay logged in until you sign out or the token expires (30 days).
- No offline write queue — mobile actions hit the API live. If you lose signal mid-tap, the action fails and shows an error; nothing is queued for later send. Captures (photos/videos in Meet Mode) DO retry on reconnection up to 3 times.
- Build environments: TestFlight / EAS-internal builds usually point at https://staging.crmown.io/api so you can test against staging without touching prod data. The store-released app always points at https://app.crmown.io/api.
Example: A field agent does property tours on her phone (Meet Mode + GPS trip tracker), then back at the office switches to her laptop to build a proposal in Finance and edit her marketing landing page in Web Studio — both surfaces that need a real keyboard and large screen. Same login, same data, no friction.
Troubleshooting
I made a contact change on mobile and it's not showing on web
Almost always a stale cached page. Mobile writes go straight to the API, but the web page you're looking at hasn't refetched since.
Fix: Hard-refresh the web page (Cmd/Ctrl+Shift+R) or click into the contact again. If still stale after a refresh, the mobile write failed silently — check the bell icon on mobile for an error notification.
I lost cell signal mid-action and the change didn't save
No offline queue — every action is a live API call. When the call fails the UI shows an error toast and reverts the optimistic state.
Fix: Re-do the action once you're back on signal. For long-form note input, copy your text before tapping Save so you can paste it back if the network drops.