Suite Modules

App Builder

Turn your WordPress site into the backend for a native mobile app. Exposes every Suite module over REST, scaffolds a React Native app, and handles auth + push notifications.

Headless WordPress

App Builder treats WordPress as a pure content + API backend. The mobile app talks to the Wigmorean REST namespace (/wp-json/wigmorean/v1/) for data; the admin stays in WP; marketing pages stay in wigmorean-pages.

Exposed endpoints

Every Suite module that has content exposes read + write endpoints appropriate to mobile use cases:

  • LMS — courses, lessons, quiz attempts, progress
  • Commerce — products, cart, orders, payment intents
  • CRM — current user's contact record, activity
  • Communities — groups, discussions, feed
  • Calendar — events, RSVPs
  • Forms — form submit

App scaffolding

App Builder generates a React Native project tuned for your site:

  1. Go to App Builder → Generate
  2. Enter app name, bundle ID, splash assets
  3. Pick which modules to include in the app
  4. Download the generated .zip
  5. Run npm install && npm start

The scaffold includes: auth flow, tab navigation, module-specific screens, theming hooked to your CSS tokens.

Authentication

App Builder uses JWT for mobile auth (not cookies). The flow:

  1. User enters credentials in the app
  2. App POSTs to /wp-json/wigmorean/v1/auth/token
  3. Server returns an access token + refresh token
  4. App stores tokens in secure storage (Keychain/Keystore)
  5. Subsequent requests send the access token as Authorization: Bearer

Tokens rotate on refresh. Revocation list is stored server-side.

Push notifications

Apps register their FCM/APNS token with the server on login. Modules can push to users:

Wigmorean_AppBuilder_Push::to_user( $user_id, [
    'title' => 'New lesson available',
    'body'  => 'Module 3: Advanced patterns is live',
    'data'  => [ 'deep_link' => '/courses/42/lessons/17' ],
] );

Offline support

The scaffold includes a local cache (SQLite + AsyncStorage) for read operations. Courses, lessons, and user progress stay available offline; writes queue and sync when the network returns.

Publishing

Deployment to the App Store and Google Play is your responsibility — App Builder generates the source, not the store listings. Documentation includes a submission checklist (screenshots, metadata, TestFlight/Play Console setup).

Need help?

Our support team responds within one business day.

Contact Support