White labelTechnology and media

Community app

Launching a community product with its moderation already working

Most community products launch the member experience and bolt on moderation later, which is when they get into trouble. Symph built both sides of this one for launch, from one shared permission model.

We keep this client’s name private. The client is real, and so is the system.

At a glance

A cross-platform community product: a mobile application, a backend service, and an administration console

Client: A community platform operator serving members through a mobile application
Industry: Community and social platforms
Status: Launched April 2026, with a further development phase underway
Engagement: Product build, then continuing development and daily production monitoring

The challenge

A community product without working moderation degrades from the day it opens.

Two complete sides, one launch
Members need a mobile experience worth returning to, and administrators need real tooling immediately.
Permissions span three clients
Members, moderators, and administrators act through a mobile app, a backend, and an admin console.
Defined three times means wrong three times
Permission logic implemented separately per client drifts, and drift in a community platform leaks content.
Suspended accounts must stop everywhere
An account restriction that only applies on one client is not a restriction.
Released mobile versions stay on phones
The platform needs control over which app versions it continues to support.

How we built it

Symph worked in three steps, each one building on the last.

One codebase, one API definition
The mobile app, backend, and admin console live in a single monorepo, with the client applications generated from the backend’s published API specification so capabilities are defined once.
One permission model in the backend
Authentication runs through a managed identity provider, and a rules-based authorisation model plus an account status gate is enforced server-side, so a restriction applies across every client at once.
Launch with real admin tooling
Content approvals, report handling, user administration, analytics, notifications, and app version management shipped as part of the launch, not after it.

Modules

01
Member mobile application
Cross-platform mobile app for discovery, profiles, and connections.
02
Member accounts and profiles
Account creation, profile management, and account status.
03
Connections
Relationships between members.
04
Content publishing and approvals
Member content with an administrator approval step before it reaches the community.
05
Reports and moderation
Community reports routed to administrators for action.
06
Notifications
Platform notifications to members.
07
Analytics
Usage and engagement measurement for the client’s team.
08
Administration console
Web console for user administration, approvals, reports, and operations.
09
App version management
Control over which released mobile app versions remain supported.

Delivery model

01
Build, then continuing development
The launch was followed by a further development phase rather than a handover.
02
Daily production health checks
Symph reviews production each morning, tracking daily active users and application exceptions.
03
Monorepo release discipline
Mobile, backend, and admin changes are versioned and released from one codebase with a shared API definition.

How it’s built

Proven architecture

A single monorepo covers the mobile app, backend, and admin console, with client code generated from the backend’s API specification, built for consistency and easy maintenance.

Secure by default

A managed identity provider, server-side rules-based authorisation, account status gating on every request, encryption, and strict access controls protect member data. Symph follows OWASP-aligned practices and the Philippine Data Privacy Act.

AI-native delivery

Symph’s engineers build with AI coding tools like Claude Code and OpenAI Codex, which is a big reason a mobile app, a backend, and an admin console launched together.

Application: NxTypeScriptReact NativeNext.jsNestJSTypeORMPostgreSQLOpenAPITailwind CSSReact Query
Google Cloud: Google CloudCloud RunCloud SQLSecret ManagerCloud LoggingIAM
Delivery and monitoring: Cloud Build
AI-native development: Claude CodeOpenAI Codex

The result

Members, moderators, and administrators operate from one permission model, across three applications, from one codebase.

33applications from one codebase
11permission model enforced server-side
DailyDailyproduction health checks
April 2026April 2026launch

Launched in April 2026
The mobile app, backend, and administration console went live together.
Moderation worked from day one
Content approvals, reports, and user administration shipped with the launch rather than after the first incident.
One permission model, every client
Restrictions and roles are enforced in the backend, so they apply across the mobile app and the admin console at once.
Monitored daily
Production health checks each morning track active users and application exceptions, so issues are found internally.
A growing partnership
The engagement has continued past launch into a further development phase.