Build-time branding
App name, icon, splash, colors, Firebase config, API base URL, and enabled modules are selected per customer flavor.
MemberHub
White-label apps for member communities.
Launch branded mobile apps for associations, societies, clubs, and community groups. Each client gets its own App Store and Play Store app, while the core product stays reusable.
Feature flags per client
History, family tree, payments, announcements, admin tools, and other modules can be included or excluded for each customer.
Admin handover
We can manage the platform and app releases while clients operate their own data through a scoped admin portal.
Feature catalogue
Modules customers can choose from.
Keep the platform modular. Every app can ship with only the features that fit that customer.
Member Management
Profiles, approvals, member directory, roles, and account status.
Announcements
Notice board, categories, push notifications, read states, and admin publishing.
Payments
Outstanding balance, annual dues, receipts, payment history, and gateway integration.
Programs & Events
Community programs, event calendar, registration, participants, and approvals.
Family Tree
Family groups, relationship mapping, member linking, and contribution tracking.
Organization Chart
Committee roles, past leaders, terms, hierarchy, and public leadership records.
Community History
Customer-specific heritage pages, timelines, founder details, and localized content.
Emergency Requests
Member emergency submissions, admin review, status tracking, and response notes.
Qibla & Prayer Times
Optional faith utility with location-aware qibla direction and prayer schedule.
Matrimonial
Optional moderated listings, approvals, detail pages, and customer-specific controls.
Admin Portal
Client-facing operations portal for members, content, payments, events, and requests.
White-Label Setup
Customer manifest, app flavors, brand assets, feature registry, and release checklist.
Delivery model
Built for separate customer apps.
Build-time customer config
Each app is generated from a customer manifest and released as a separate store listing.
Reusable feature library
Core membership features live in shared packages and are assembled per customer.
Scoped admin handover
Clients manage their operational data while platform ownership remains with the provider.
Future flexibility
Home layout starts with style1 and leaves style2 as a clean extension point.