Why my path from native iOS engineering through product management now leads into React Native and Expo for cross-platform mobile apps.
My career has moved through a few distinct chapters: iOS engineer, product manager, independent builder, and now React Native / Expo engineer. On paper that can look like a set of pivots. In practice, it feels like one continuous thread.
I like building tools that people can hold in their hands, open every day, and trust with small but important parts of their lives. That started with iOS, sharpened through product management, and now continues with React Native and Expo.
The quote I keep coming back to is simple:
Give people wonderful tools, and they'll do wonderful things.
That belief still describes the work I want to do. The stack is changing. The standard is not.
iOS taught me craft.
It taught me that tiny interaction details matter. That performance is part of the user experience. That an app should feel calm and predictable, not just technically correct. Working with Swift, UIKit, and later SwiftUI gave me a strong sense for what polished mobile software should feel like.
At Unified Practice, that craft had real weight. We were building healthcare tools used in clinics, where confusing flows or unreliable behavior could create actual stress for practitioners. That kind of work makes you more serious about clarity.
It also made me curious about the product side. I did not just want to know how to build the feature. I wanted to understand why it mattered, who it helped, and whether it was the right thing to build at all.
Moving into product management changed my default question from "how do we ship this?" to "should we ship this, and what outcome are we trying to create?"
For roughly two years, I owned mobile product work across iOS, iPadOS, and Android. I wrote specs, prioritized roadmaps, worked with engineering, QA, design, support, and stakeholders, and learned to connect user needs with technical reality.
That chapter made me a better engineer. It gave me more patience for tradeoffs, more respect for research and data, and a much clearer sense that software quality is not only about architecture. It is also about choosing the right problem.
After returning to hands-on building through Smart Code Studio, I kept running into the same practical challenge: I wanted to ship thoughtful mobile products on both iOS and Android without splitting my attention across two completely separate native codebases.
React Native and Expo became the obvious next step.
Expo gives me the product velocity I want as an independent builder. React Native gives me a shared mobile foundation without asking me to forget what good native apps feel like. My iOS background is still useful every day: in performance decisions, navigation choices, platform expectations, release quality, and the small details that make an app feel considered.
The goal is not to abandon iOS. The goal is to bring that iOS taste into cross-platform work.
iBeauty is where this transition became concrete.
It is a finance app for beauty professionals, built with React Native, Expo, Supabase, in-app purchases, and push notifications. It runs on iOS and Android, but the product standard is the same one I learned from native iOS: keep it clear, fast, and focused on the user's real workflow.
The app is not trying to be everything. It helps salon professionals track daily income, expenses, savings, and monthly profit in a way that feels simple enough to use after a long day of work.
That is the kind of product I want to keep building: practical tools for real people, with enough care in the details that the software starts to feel lighter than the problem it solves.
AI is still interesting to me. I have built experiments like COPILOT and OmniAssistant, and those projects taught me a lot about automation, prompts, backend workflows, and product ambiguity.
But AI is not the center of my professional positioning right now. It is more of a hobby and exploration space. My core direction is mobile: iOS as the foundation, product thinking as the lens, and React Native / Expo as the way forward for cross-platform apps.
That feels more honest. It also feels more useful.
I am still the same kind of builder I was when I fell in love with iOS: someone who cares about tools, taste, and usefulness.
The difference is that now I can see the whole path more clearly. Native iOS gave me craft. Product management gave me judgment. React Native and Expo give me reach.
That combination is where I want to spend the next chapter.