Module · App Connector

ExpertPress App Connector

Status: In testing · Plan: Free

App Connector lets a branded mobile application for clients and specialists work with your ExpertPress site. It adds secure app sign-in, the app endpoints for accounts, bookings and the specialist cabinet, and optional push notifications to phones (through Expo) and to web browsers. Marketplace rules do not change: the app uses the same bookings, payments and messages as the website.

Key capabilities

  • App sign-in for clients and specialists with revocable sessions. Only applications on your allowed list can sign in.
  • App endpoints for the account and its settings, bookings and orders, meeting links, reviews, and the specialist cabinet (calendar, profile and service editor, statistics and finance views where the related modules are installed).
  • Booking commands from the app: accept, decline or cancel a booking and set a meeting link, using the same checks as the website. Can be switched off.
  • Push notifications to phones through the Expo push service: new and changed bookings, unread messages, complaint events and meeting reminders. Notification texts come from fixed templates; message bodies and names written by users are never sent.
  • Browser push notifications (a separate switch) for signed-in visitors whose theme shows the notification settings block.
  • Status panel showing storage readiness, active app sessions and devices, the push queue for the last 24 hours and the last worker runs.
  • Emergency sign-out of every app session with one action.

Requirements

  • Requires Plugins: expertpress (ExpertPress Core). WordPress 6.0+, PHP 7.4+.
  • A branded mobile application built for ExpertPress. The connector is the server side only; it does not include the app.
  • Compatible module versions. If Payments, Messages, Promotion or Video is installed (even inactive), its build must declare compatibility with the connector. Otherwise app access stays off and administrators see “ExpertPress App Connector transport is disabled. Install compatible Core, Connector and app module builds.” with the reason.
  • WP-Cron (or a real cron calling it) for push sending, receipt checks and hourly cleanup.
  • Browser push works only with the standard WordPress session storage. A site with another session manager sees an error on the Web push page and nothing is sent.

External services

  • Expo Push Notifications (optional). Used only when phone push is enabled and an Expo access token is set. The site sends to https://exp.host/--/api/v2/push/send and checks delivery at https://exp.host/--/api/v2/push/getReceipts. Data sent: the Expo push tokens of the recipient's devices, notification text from fixed templates, sound and lifetime settings, and opaque identifiers that open the right screen in the app. Receipt checks send ticket identifiers only. Terms: https://expo.dev/terms · Privacy: https://expo.dev/privacy
  • Browser push services (optional). When Send browser push notifications is on, encrypted notifications go to the push endpoint chosen by each visitor's browser (the browser vendor's push service). The site signs them with its own keys, generated automatically.

Who sees what

  • Clients and specialists sign in to the app with their site account. They see their bookings, messages and account in the app, and receive push notifications if they allow them on the device. Specialists can also manage their calendar, profile and services from the app when those features are on.
  • Visitors on the website see nothing new unless the theme prints the browser notification settings block (an element with the data-ep-web-push attribute); then signed-in users can turn notifications on for that browser.
  • Administrators (manage_options only) get the Mobile application (Мобільний застосунок) tab under ExpertPress → Settings and the Web push (Веб-пуші) page under WordPress Settings. ExpertPress Managers do not see them.

Sessions

  • An app access token lasts 15 minutes and is renewed automatically with a refresh token.
  • A session ends after 30 days without use, and in any case 90 days after sign-in. A developer can change these periods with the filters expertpress_mobile_access_ttl, expertpress_mobile_refresh_idle_ttl and expertpress_mobile_absolute_ttl.
  • Closing or blocking an account, or removing an application from the allowed list, stops its app access on the next request.

Data and removal

  • Deactivation stops the scheduled jobs. Sessions, devices and settings stay, so reactivation continues where it stopped.
  • Deleting the plugin removes app sessions and tokens, devices, phone and browser push queues and subscriptions, push keys and credentials, settings and scheduled jobs. Marketplace records and other modules' data are kept.

Next