Two Birds Code · why this exists
A native app for Fluent Community, with the WordPress plugin and the build dashboard we wished someone had made. One lifetime license. Your source, your store listing, your app — whether you keep paying or not.
The story · how we got here
Where we started
We’ve been running an online community for years. Started back with BuddyPress, grew with BuddyBoss — the whole journey. Forums, groups, member profiles, the works. And for a while, it was fine.
But we always knew the tech was dated. And when we started looking at our options for a mobile app, it got worse. Webview wrappers that felt slow. Generic white-label apps you couldn’t really customize. Expensive SaaS platforms where you had zero access to the actual code. And the ones that did give you “dev access”? Limited. Locked down. Basic.
Stop paying, and you lose “your” app. The one your members use every day. The one with your brand on it. Gone.
That was the thing that kept us stuck. Our members lived in the app, and every option had the same catch. The cost added up fast for a small community like ours. So we started asking ourselves — what if we just… built our own?
The switch
When we found Fluent Community, it clicked. Modern. Fast. Actually maintained. Built on a clean codebase by a team that ships. It was everything the others used to promise but never quite delivered.
But there was no native app for it. Not one we could actually own. There were options — managed services that build and deploy an app for you. They’ll put your colours and logo on it, sure. But you don’t get the source code. You don’t control the builds. You’re back to renting someone else’s platform. We didn’t spend all that time leaving one locked-in setup just to settle for the lazy option.
What we built
So we spent months planning and building. Not just an app — an app we could actually manage ourselves. One that matched our Fluent Community site feature-for-feature. Feed, messaging, spaces, profiles, courses, push notifications — all native. Not a webview wrapper. A real React Native app.
Along the way we built the tools we wished we had — a dashboard to manage everything from the browser, instant updates we could push without waiting on App Store review, a way to add new features without breaking the core, and a plugin that lets you reshape the app from WordPress while watching it change. We built all of it because we use all of it. Every day. For our own community.
This isn’t a product someone dreamed up in a boardroom. It’s a tool we needed, and we made it good enough to share.
The difference · in one table
Who it’s for · pick the one that sounds like you
Two kinds of people buy this. The license is the same for both — a one-time cost per site. What changes is who does the building and who pays for it.
Community owner
You run a community on Fluent. You don’t want another subscription that disappears if you stop paying. You want something real — an app with your brand, in your App Store listing, that you actually own.
What you get
An app with your brand, in your store listing, that keeps working whether or not you ever pay us again.
Everything the app does is on The App page. How you shape it without a developer is on The Plugin.
Developer
Instead of building from scratch every time, grab a license per client, white-label it, customize it with modules, and charge them for setup and ongoing maintenance. Their builds, their updates, their dashboard — you manage it all.
What you get
A product you can resell, a fleet you can run from one screen, and margin that is yours to set.
The fleet view and the build tooling are on The Dashboard. The add-on modules are listed in the shop.
Not a SaaS
Your first year of core updates is included. After that, renew just the updates for a small yearly fee — not the app itself. Renew or don’t, it keeps working. You’re only paying to stay current, never to keep what you already have.