Dev Bundle

I’ve just purchased please can you confirm and let me know thanks

Hi! — happy to confirm all of this clearly.

License / ownership

Yes to all of it:

• Store the full source in your own private GitHub repository, permanently — that's fine.
• Modify it and work with third-party React Native developers — absolutely, it's your code to build on.
• Publish through your own Apple and Google developer accounts — yes, the app ships under your own developer accounts and your own listings.
• Keep running the app if you don't renew — yes. The annual renewal covers ongoing updates and support only; it is not a kill switch. If you choose not to renew, your app keeps working and you keep everything you already have — you just stop receiving new core updates from us.

One honest heads-up, purely practical: the app is built with a core plus a module system. If you (or your developers) edit the core files directly, you'll have trouble pulling in our future updates cleanly — same as editing any core WordPress plugin. You rarely need to, though, because the module system is built specifically so your developers can add and change features alongside the core without touching it. That keeps your customizations and our updates from colliding. So: fully yours to modify, and there's a clean lane to do it in.

BetterMessages

Straight answer: not automatically. Out of the box, the app's Message button opens Fluent Community messaging (which is what the core is wired to), and the unread count shown is Fluent's. It won't switch itself over to BetterMessages just because BetterMessages is installed on your site.

The good news is it can be integrated, and cleanly. The Message icon — including its unread-count badge — is built to support modules, meaning it can be pointed at a different messaging system. BetterMessages ships with a full API (conversations, threads, users, push notifications), so your React developers have a real foundation to build a module against. Roughly what that involves:

1. Connecting the chat screens to BetterMessages' API instead of Fluent's (the straightforward part).
2. Handling BetterMessages' live/real-time layer for instant delivery and typing/read indicators (the part to budget for).
3. Pointing the Message icon at it and feeding its unread count into the badge (clean, since the icon supports modules).

So it's a defined project rather than a flip-a-switch feature — but it's exactly the kind of custom integration the module system exists for, and you're not locked to Fluent. We did the same thing to add a WooCommerce cart alongside the core, so there's a proven pattern for it.

Blog section

Here's how it works today, honestly:

• Search by title/content — not surfaced in the current build. The blog runs on the standard WordPress API, which does support searching by title and content, so the capability is there underneath — it just isn't shown on the blog screen yet. It's a natural enhancement to add on top of what's already in place, rather than something built from scratch.
• Categories & tags — categories already display on posts. Tags aren't shown yet, and neither is tappable at the moment. Making both appear and link (tap a category → see all its posts) is a strong, sensible enhancement for the blog section, and it builds directly on data the app is already pulling in.
• Links inside articles — yes, this already works the way you'd want: links to anything inside your community (spaces, profiles, courses, member posts) stay in the app, and links to outside websites open in the device browser. The one current exception is a link from one of your blog articles to another blog article — that opens in the browser today, but it can be adjusted to stay in-app.

So the blog reading experience is solid right now, and search, tappable categories/tags, and blog-to-blog links are all realistic enhancements that build on what's already there.