Overview 🔗

SIApps is an inclusive community platform backed by GP Ansor, serving 50k+ monthly active users across mobile and web. Features include event management, discussion forums, member directories, academy programs, and financial aid modules. Led engineering from architecture to production.

Role & Context 🔗

As Tech Lead and Product Engineer, I built the mobile app and internal web dashboards from scratch. GP Ansor needed a unified platform for their community programs—managing events, membership, education, and financial services—and I delivered a solution that now serves 50k+ monthly active users.

Key Features 🔗

Home 🔗

Dynamic menu with configurable ordering (controlled via Firebase Remote Config) for economy, academy, consultation, vocation, event, and worship sections.

Community 🔗

YouTube video and image gallery with optional external platform integration, all configurable via Remote Config.

Academy & Ansor Programs 🔗

Program listing, application flows, history tracking, and member card management with photo updates and printable cards.

Economy & Business 🔗

Business registration and related master data management for community enterprises.

Legal & Financial Aid 🔗

Dedicated modules for legal aid, tax aid, financial aid, and consultation with submission flows.

Force Update 🔗

App version enforcement via Remote Config min_version, ensuring users stay on compatible versions.

Help Center 🔗

WebView to static support pages and WhatsApp integration with predefined messages (configurable via Remote Config).

Build Notes 🔗

Remote Config as a Feature Toggle 🔗

The home menu, community section, and help center all use Firebase Remote Config to control content URLs and visibility. This means the product team can reorder home menu items, toggle community features on and off, or update WhatsApp predefined messages without an app release. This was essential for a community app where program availability changes frequently.

API Response Validation 🔗

Every API response is validated through Zod schemas organized per service module, with centralized enforcement in the API client. When the backend changes a field or adds a nullable property, the app throws a clear error in development rather than silently breaking in production. This pattern was consistent across both the SIApps and Relinvest codebases.

Multi-Environment CI/CD 🔗

EAS Build with staging, beta, and production channels. Force update is handled via a min_version Remote Config key — when users are on an outdated version, they’re prompted to update rather than encountering runtime errors from API contract changes.

Scale 🔗

50k+ monthly active users across mobile and web platforms.