An app shaped around how your brand works
When the standard layout is not enough, we build a community app around your actual workflows and ship it to both stores.
Push
Your weekly issue is ready to approve
Some communities do not fit a feed and a group list.
A temple network coordinating events across three countries, a coin with token gated tiers, a college running intake every August. Each of these has a workflow that a standard community layout can approximate but never quite fit, and the gap shows up as members doing things in the wrong place.
A custom app closes that gap. It is your app, on your developer account, in both stores under your name, with screens built around what your members actually do. Underneath it runs the same platform and the same agents, so you get the bespoke experience without the bespoke maintenance burden.
At a glance
- Platforms
- iOS and Android
- Store account
- Yours
- Typical timeline
- 6 to 10 weeks
- Push notifications
- Segmented and rate limited
- Offline support
- Cached reads, queued writes
- Availability
- Enterprise, or Premium as an add-on
Everything included
Everything below works out of the box, with no custom development required.
Published under your developer account
Your name in both stores, your listing, your reviews. We build and submit, you own the account and the app record, so there is no hostage situation if you ever want to take it elsewhere.
Screens built for your workflow
Whatever the core action is for your community, that becomes a first class screen rather than something buried three taps deep. Event check in, donation, token verification, class booking, order history.
Push notifications that are worth allowing
Segmented by group, geography and behaviour, and rate limited so people keep them switched on. Agents can trigger them, but only within limits you set.
Offline and low bandwidth handling
Content caches and posts queue when a connection drops, which matters for communities spread across regions where connectivity is uneven.
Deep links from everything you already run
Links in your emails, packaging, posters and ads open the right screen in the app, or the web version if the app is not installed. No dead ends.
One dashboard for web and app
Your team manages both from the same admin. Agents run across both surfaces with a single activity log, so nothing is tracked twice or missed.
Every feature is yours to turn on or off
Rename any section into your own language, reorder the tab bar, hide what you do not need and add what you do. A temple network and a coin do not need the same five tabs.
Media handled properly on a phone
Photos, long video, short form clips and documents, all transcoded for mobile and streamed adaptively so a member on a weak connection still gets something watchable.
Whatever your community actually does
Turn on what fits, rename it into your own language, and hide the rest. No two communities use the same five tabs.
Notifications
- In app notification centre with unread counts per space
- Push segmented by group, geography, tier and behaviour
- Rate limits so people keep notifications switched on
- Quiet hours per member, respected across time zones
- Agents can trigger a push only inside limits you set
Events
- Create events with capacity, ticketing and waitlists
- RSVP, calendar export and automatic reminders
- QR check in at the door, works offline
- Recurring events for weekly classes or services
- Post event threads so the conversation keeps going
Newsletters
- Written by the Newsletter Agent from the week that happened
- Sent from your own address with your branding
- Per group and per region editions, not one for everybody
- Delivered at each member’s own best hour
- Open, click and reply reporting in the dashboard
Chat and channels
- Dedicated chatrooms for live conversation
- Named channels for a topic, project or cohort
- Direct and group messaging between members
- Threaded discussion that stays readable a week later
- Full text search across everything a member can see
Groups and access
- Public groups, private groups and hidden groups
- Access by invite, purchase, membership tier or wallet
- Sub communities with their own moderators and rules
- Roles and permissions set per group
- Member directory scoped to what each role may see
Posts and media
- Text posts, polls, questions and link previews
- Images with albums and captions
- Long form video with adaptive streaming
- Short form vertical clips with a swipe feed
- Documents and PDFs with in app preview
Documents and knowledge
- Pinned resources per group so answers stay findable
- Version history on shared documents
- The Support Agent answers from these files with a source link
- Download controls per role
Customisation
- Rename every section into your own language
- Reorder or hide tabs per role
- Colour, typography and corner style from your brand
- Custom screens for the workflows your community revolves around
- Feature flags so you can roll something out to one group first
How it goes live
- 1
Scope the workflows
A short discovery to work out which two or three actions your community actually revolves around. Those become the app rather than a feature list.
- 2
Design against your brand
Screens designed in your existing design language, reviewed with your team before anything is built.
- 3
Build, test and submit
We build both platforms, run a beta through TestFlight and Play internal testing with a group of your members, then submit under your developer account.
- 4
Launch and hand over
You get the dashboard, the analytics and the agent controls. We stay on for updates and store submissions.
Included with this solution
- iOS and Android under your developer account
- Custom flows, screens and notifications
- Deep links from your existing marketing
- Same agent layer, same dashboard
Custom App specifics
Who owns the app?
You do. It sits in your App Store Connect and Play Console accounts under your legal entity. We are the build partner, not the owner.
What happens when the platform updates?
Platform updates flow through automatically because the app runs on the same backend as everything else. Store submissions for OS level changes are handled by us as part of the engagement.
Can we start on the whitelabelled website and move to an app later?
That is the usual path, and the sensible one. Run the community on the web first, learn which workflows matter, then build the app around what you have actually observed rather than what you guessed.
Ways to run the same platform
- Whitelabelled Website
Your own branded community, live in days
Your domain, your logo, your colours. Our name appears nowhere.
- In App SDK
Drop a community module into your product
Feed, groups and support threads inside your app, using your own auth.
- Integrations
Connect your store, CRM, chat and help desk
Agents answer from your real data, not from a guess.
See custom app with your own brand on it
Book a demo and we will set it up with your data before the call.
Thirty minutes. No credit card, no obligation.