Work
What I have built
New Dongtan Church Platform
A church-wide portal and mobile app driven by an eight-tier permission model
Web · iOS · Android
RESCENE ARCHIVE
Official content scattered across platforms, gathered into one timeline
Web · iOS · Android
Let's Do Math
A study app that counts only the time actually spent focused
iOS
Syncronome
A metronome that keeps every device on the same beat within ±10 ms
iOS
Capabilities
What I cover
Product design
It starts with deciding what to build. User roles, the permission structure, the data model, and the screen flow go into a document before any code gets written.
Web and mobile
Web alongside iOS and Android. I have run a single product across three surfaces at the same time.
Backend and infrastructure
Database schemas and access policies, server functions, and scheduled pipelines. Permission and data rules are enforced in the database, not in the application.
Release and operations
Getting through App Store, Google Play, and ONE Store review, pushing urgent fixes over a self-hosted channel, and tracking the running system through audit logs.
How I work
How I work
Push the rules down to the database
Permission checks do not end at conditional rendering. They are re-verified in database policies and server functions, so bypassing the client does not open the data.
Do not trust what cannot be measured
Whether it is focus minutes or beat error, a number reported by the client is not taken at face value. The server recomputes it, or it gets recorded and cross-checked for real.
Leave the reasoning behind decisions
Why this choice, why this value — it goes in a document. When something goes wrong, the retrospective becomes policy so the same mistake does not repeat.
Never design against the user
No dark patterns, granular consent, and browsing without an account. Accessibility is not something bolted on at the end.