Getting started

First-run flow

After activation, open Orravo Core → OMobile. The dashboard tabs cover Devices, Push, Analytics, Crashes, Remote Config, Flags, Announcements, and Settings.

Minimum config to ship a build

1. Settings → API - confirm the REST namespace omobile/v1 is reachable at /wp-json/omobile/v1/
2. Settings → Push - paste either an FCM v1 service account JSON, an APNS .p8 key (with Team ID + Key ID), or an Expo access token
3. Settings → App Versions - register the minimum and current app version per platform so the /app-version endpoint can return force-update flags
4. Remote Config - add at least one key (for example maintenance_mode: false) so the app has something to fetch on first launch

Wire up the app

Every device call includes X-Om-Install-Id: <uuid>. Generate the UUID once on first launch and persist it in secure storage.

Login example:

POST /wp-json/omobile/v1/auth/login
Content-Type: application/json
X-Om-Install-Id: 9b1c3d8a-...

{ "username": "user@example.com", "password": "..." }

Authenticated calls add Authorization: Bearer <access_token>.

Register the device

As soon as you have a push token, POST it to /devices/register so push providers can address that install. The same call updates platform, app version, and locale on every launch.