Mobile apps should feel like they belong in your hand.

Problem. A real mobile app with releases, QA feedback and requirements moving while the experience still had to feel stable.

Why it matters. This is where mobile ownership becomes concrete: app state, edge cases, native constraints and tiny UI decisions that change daily use.

Role. Owned large parts of the mobile work, then adjusted to team setups where responsibilities shifted between solo delivery, feature work and handoffs.

Problem. A small app for testing when haptics help, when they get noisy and how much feedback an action deserves.

Why it matters. It is hard to talk about 'feel' from a screenshot. On a phone, the difference becomes much easier to judge.

Role. Mapped control states to tactile feedback and kept the interaction model simple enough to judge by feel.

Problem. A prototype for turning device movement into readable, steady UI.

Why it matters. Sensor data is messy. The useful work is choosing thresholds, smoothing and feedback that feels predictable.

Role. Mapped motion input, thresholds, smoothing and animated response inside a React Native surface.

Problem. A tiny app for practicing the details that make even a simple interface feel cared for.

Why it matters. Small components show quickly whether type, color, state and timing still feel right under real taps.

Role. Treated the counter like a small design system: tokens, accessible states and feedback that stays consistent.

Problem. Small local helpers that make useful test states quicker to reach, so there is more time to check the app on-device.

Why it matters. When setup is slow, small interaction bugs are easier to miss. Faster setup makes release checks less painful.

Role. Kept the tooling focused on scenario setup, mobile testing and release confidence.