HubRelay

The community's real logic and data already lived inside WordPress/BuddyBoss — a companion mobile app couldn't reasonably reimplement all of that. HubRelay is the bridge layer that resulted: an API connecting the WordPress/BuddyBoss community platform to a native mobile app, exposing profiles, groups, activity feeds, and messaging through clean REST endpoints while keeping WordPress as the single source of truth, without duplicating its business logic.

What I Built

• Custom endpoints on top of WordPress/BuddyBoss — extending existing plugin data for mobile consumption
• Activity feed API — posts, comments, and likes surfaced through REST
• Groups and profiles API — membership, profile fields, and group activity
• Messaging bridge — private messages accessible from the mobile client
• Auth bridge — token-based authentication mapped onto WordPress sessions, so users log in once and stay in sync across both surfaces

Tech Stack

• Platform: WordPress, BuddyBoss
• Language: PHP
• API: REST (WP REST API extensions)
• Auth: JWT bridging WordPress sessions

Key Decisions

• Built a bridge API layer rather than reimplementing community features natively in the mobile app, keeping WordPress/BuddyBoss as the single source of truth and avoiding logic duplication that would drift out of sync over time
• Mapped mobile auth tokens onto existing WordPress sessions instead of building a parallel auth system, so users logged in once and stayed consistent across both the website and the app

Outcome / Impact

Enabled a mobile app to fully mirror the community site's functionality without duplicating business logic — the mobile client stayed thin while WordPress remained the system of record.