WordPress Chat Mobile App: iOS and Android for Your Site

November 10, 2025 · 7 min read

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#

Every app is yours from the very first build — there is no generic "Better Messages" app that members download and point at your site. The app builder lives in your WordPress admin under Better Messages → Mobile App, it is included in the WebSocket plan at no extra cost, and it is currently in alpha.

What you set on the settings page:

Your app name and icon on the App Store / Play Store.
Your splash screen and its background color, your logo on the login screen, your notification icon on Android.
Your own bundle identifier, registered under your own Apple Developer and Google Play accounts — you own the listing.
Your domain as the API endpoint (the app talks to your WordPress site, not to anyone else's).

Builds are compiled on our build server, so there is no Mac, Xcode, or Android Studio in the loop. You connect the App Store Connect API and a Firebase project once, press build, and get a development build you install by scanning a QR code with your phone — an APK on Android, and on iOS any device registered in your developer account. Production builds come out as a TestFlight upload on iOS and an AAB for the Play Console on Android, and the Android signing keystore can be generated right on the settings page.

The only accounts you pay for are the stores' own: the Apple Developer Program (99 USD / year, required on iOS even for testing on your own device) and a Google Play developer account (25 USD one-time, needed only when you publish — testing an APK on your own phone is free).

The full walkthrough, screen by screen, is in the iOS and Android setup guides.

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#

You build the app once in Better Messages → Mobile App, publish it under your own developer accounts, and members install your app from the App Store / Play Store by name. There is no site-URL entry screen to get through: the app is bound to your domain at build time, so the first thing a member sees is your splash screen and a login form.

Members sign in with the WordPress username and password they already use on your site. The app talks to your site's REST API for everything — it has no separate database and no separate user list.

Store updates work the same way as the first release. When you want a new version out — a fresh icon, a renamed app, a newer Better Messages release — you press build again and upload the result yourself. The listing stays entirely under your control.

Frequently asked questions#

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

Yes — the app builder is part of the WebSocket plan, and an active license is what unlocks building. Inside the app, the WebSocket version is also what powers instant delivery, voice / video calls, and the typing indicator. Push notifications are the exception: they reach the phone through APNs and FCM directly, not through the relay.

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 the app to the App Store under my own developer account?#

Yes — that is the only way it works. The app is built with your bundle identifier, signed with your credentials, and submitted from your own Apple Developer and Google Play accounts, so the listing belongs to you. Store updates are yours to run as well: rebuild in the admin, upload the new binary. Nobody at Better Messages sits in the middle of your release.

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.