About

I'm not here to “ship an app” for the sake of it. I build when something about day to day phone use keeps bugging me. Clunky flow. Extra taps. UI that fights you. A job that should be simple and is not. That kind of thing.

I end up asking the same questions over and over. Why does this feel harder than it needs to be? Has nobody bothered to clean this up yet? If a team at Apple actually cared about this use case, what would they do? Those questions are what pulled me into iOS work in the first place.

I like software that feels obvious when you open it. Calm. Focused. Not shouting for attention. One job done well, in a way that feels natural on the phone.

Where ideas come from

I rarely start with a feature list. I start with whatever felt off in real life. A repeat task. A moment of mental overhead. Something cluttered that should feel lighter. I wonder what is actually annoying people here, what people do on autopilot that could be smoother, where the weight is that does not need to be there, and what calm would look like instead of busy.

From there I sketch toward removing friction instead of piling on more surface area. A lot of what I want to build looks small from the outside. Tight tools. Local first when it fits. Interfaces that only ask for what they need.

Apple's product craft is a north star for me. Tight integration. UI that respects your time. Hardware and software that feel like one thing.

How I like to work

If you need a manual we're probably already off track. The screen should explain what to do next. Adding features is easy and holding the line is the hard part. Local first and privacy minded beats collect everything most of the time. The best stuff feels like it was always supposed to live there.

I put real effort into how an app feels, not only whether the logic checks out. Structure and polish up front usually save me pain later. I don't rush past that part.

Function matters. So does the bit you notice before you even think about it.

Why iOS

I stay on Apple's platforms because the constraints help. Same design language. Solid tooling. SwiftUI for UI I can iterate on without losing my mind.

It's a good place to care about detail. Motion. Type. Accessibility. The small stuff users shouldn't have to articulate. I want apps that work. I also want them to feel at home on the device they sit on.

Getting it to run is table stakes. Getting it to feel like it belongs here is what I'm aiming for.

What you'll see in my work

If you click around the projects you'll see a few habits. UI that stays out of the way. Apps built for a purpose instead of a feature checklist. Tools I would actually use in a normal week. Code and layout kept organized on purpose. UX that earns trust over loud demo reel energy.

Nothing here started as a generic tutorial brief. Each one was a real itch I wanted gone.

Long term

I plan to keep shipping small considered apps. The kind that make regular days a little less annoying. Over time this site is partly a portfolio and partly a record of how I think and build.

To me the best software doesn't announce itself.

It shows up, does the job, and gets out of the way.

That's the bar I'm holding myself to.