HELLO, I'M MULIA.
I BUILD SOFTWARE
THAT WORKS.
7+ YEARS BUILDING ANDROID APPLICATIONS
FOR PRODUCTION AND ENTERPRISE ENVIRONMENTS.
[LOCATION] JAKARTA, INDONESIA
[FOCUS] ARCHITECTURE, SCALABILITY
I build Android applications where correctness matters. Most of my career has been in enterprise banking — systems used by thousands of people to make real financial decisions. That context shapes how I think about architecture, state management, and maintainability.
Things I've built, maintained and shipped.
BRISPOT PEMRAKARSA
Enterprise Android application used by Relationship Managers at Bank BRI to initiate loan proposals, analyze customer data, and manage submissions. Built and maintained across multiple production cycles.
FRIDGO
Cross-platform smart refrigerator inventory application built using Compose Multiplatform (KMP). Features Supabase auth, canonical metric storage, and multilingual support.
GOOD SOFTWARE IS BORING IN PRODUCTION.
[01] PREDICTABLE ARCHITECTURE
A feature should have clear boundaries. UI should not own business logic. Business rules should not depend on Android UI. Data access should have explicit contracts. The goal is not architectural complexity — the goal is easier reasoning.
[02] EXPLICIT STATE
UI state should be a single source of truth. State transitions should be understandable, predictable, and isolated from side effects. Implicit state is the most common source of bugs in long-lived applications.
[03] SMALL RESPONSIBILITIES
Components should have focused responsibilities. Business logic should be independently testable without a device, an emulator, or a running UI. Code that can be tested is code that can be maintained by someone else.