Skip to main content

WordPress Chat Mobile App: iOS and Android for Your Site

· 6 min read
Andrij Tkachenko
Creator of Better Messages

Site owners running paid communities, course academies, and vendor marketplaces consistently hit the same wall: members live on their phone, not their browser. A site without a mobile app loses the daily-engagement signal — push notifications never reach the user, the site tab goes stale, members drift to Discord or Slack where the app experience is native. Better Messages ships native iOS and Android apps built on Capacitor that members install from the App Store / Play Store and use as the on-the-go front door to your community's chat.

What the mobile app does​

The Better Messages mobile app is a real native app — App Store / Play Store install, app-store-grade UX, push notifications, deep links, background sync. It is not a wrapped browser.

Inside the app, the chat experience is the messenger members already know from the web:

  • Inbox of conversations — same threads, same unread state, same group chats.
  • Real-time message delivery via WebSocket — instant message arrival when the app is open.
  • Push notifications when the app is closed or backgrounded (APNs on iOS, FCM on Android).
  • Voice and video calls — same calls members place on the web, now native on the phone.
  • File attachments — upload from camera, photo library, or files app.
  • Offline support — read history offline, queue messages for send when connectivity returns.
  • Mobile-only UX — bottom tab bar, full-screen threads, swipe gestures.

How the app works (Capacitor + WebSocket)​

The app is built with Capacitor — Ionic's native runtime that wraps a web view with native APIs (push, camera, files, notifications, deep links). The chat UI is the same React codebase that powers the desktop messenger, packaged into the native shell.

The underlying transport is the WebSocket version's socket.io relay — the same realtime layer that powers desktop. The mobile app maintains a persistent connection for instant delivery while open, and falls back to native push when backgrounded.

The result: a single codebase, two stores, consistent UX across desktop / mobile / tablet.

Push notifications​

Native push notifications work on both the free and WebSocket versions of Better Messages — the mobile app uses APNs (iOS) and FCM (Android) directly, not the WebSocket relay. With the WebSocket version, real-time message delivery while the app is open is instant; without it, messages arrive via AJAX polling every few seconds.

Voice and video calls​

The app supports both one-on-one and group voice / video calls inside any thread. Native phone notifications announce incoming calls; the call UI is full-screen with mute / camera-toggle / speaker / end-call controls. The same calls work on desktop and mobile transparently — a call started on desktop continues if you switch to the phone.

White-label your own branded app​

By default the app is "Better Messages" branded. For paid sites that want their own app on the stores, the WebSocket license includes white-label rebuild support:

  • Your app name and icon on the App Store / Play Store.
  • Your splash screen, theme colors, and login screen branding.
  • Your domain as the API endpoint (the app talks to your WordPress site, not to anyone else's).
  • Your Apple Developer / Google Play accounts publish the app (you own the listing).

Talk to support about the white-label process — there is a one-time setup that covers icon / brand / signing keys.

Which community / LMS / marketplace plugins are supported in the app?​

Every integration that works on the web works in the mobile app — the integration runs server-side on WordPress, the app is just a different client. BuddyPress, BuddyBoss, PeepSo, Ultimate Member, FluentCommunity, LearnDash, LearnPress, Tutor LMS, MasterStudy, Dokan, WCFM, WC Vendors, MultiVendorX, WP Job Manager, HivePress, Directorist, GeoDirectory, Classified Listing, Motors, and the rest — all show up correctly inside the app.

Installing the mobile app for your site​

Members install the app from the App Store / Play Store. The first time they open it, they enter your site's URL (or scan a QR code, or use a deep link). The app talks to your WordPress site's REST API for everything — the app does not have a separate database.

For white-label sites, members download your app instead — same flow, but no URL entry because the app is hard-coded to your site.

Frequently asked questions​

Does the mobile app require the WebSocket version of Better Messages?​

The app installs and runs on both the free and WebSocket versions. The WebSocket version unlocks real-time delivery, voice / video calls, and the typing indicator. Push notifications work on both.

Will the app work alongside the BuddyBoss / BuddyPress / PeepSo native apps?​

The BuddyBoss native app uses BuddyBoss's own messaging stack, not Better Messages — they are separate apps. Members who use the BuddyBoss app for community + the Better Messages app for chat have two apps installed, which is unusual. Most sites pick one: BuddyBoss-app sites typically use BuddyBoss messaging; sites that have moved messaging to Better Messages typically use the Better Messages app for the messenger.

Can I publish a white-label version of the app to the App Store under my own developer account?​

Yes — that is the standard white-label flow. You own the App Store listing, the Better Messages team provides the rebuild and signing-key handoff. One-time setup; ongoing app-store updates handled by the Better Messages team.

What WordPress versions are supported?​

WordPress 5.9+ on the backend; iOS 13+ and Android 8+ on the app side.

Can members log in with the same WordPress credentials?​

Yes — the app uses WordPress authentication. Members log in with their WP username / password the first time; the app stores a long-lived token for subsequent launches.

What happens if the user changes their password?​

The stored token is invalidated; the app prompts for re-login on the next launch.

See also​

Install Better Messages from WordPress.org →