I still think a lot in terms of Apple platforms. Swift, SwiftUI, and tvOS have shaped the way I look at interaction, layout, and software quality, even when the project is just a browser toy or a tiny utility.
Most of the things here are intentionally small. That is part of the appeal. Small projects leave nowhere to hide, which makes them a good place to practice taste, restraint, and attention to detail.
Approach
Rules that keep hobby projects enjoyable.
The goal is not to industrialize every idea. It is to make the small thing good enough that it feels worth returning to.
Make the small thing feel finished
If a project is intentionally small, that makes details matter more. Input feel, spacing, naming, and visual rhythm have nowhere to hide.
Give every tool one job
The most satisfying tools tend to be narrow. They know what they are for, they do not overexplain themselves, and they stop before they become chores to maintain.
Leave room to tinker again
I want these projects to stay pleasant to revisit. That usually means direct structure, fewer moving parts, and code that still makes sense after some time away.
More context
What shapes the things I put here.
Even casual projects carry the fingerprints of the tools and platforms I care about most.
Why this site exists
This is not a portfolio in the usual sense. It is a place to keep the small things I make because they seem fun, useful, or oddly satisfying enough to finish.
Some entries will be tiny games. Some will be small tools. Some will just be interface experiments or notes from trying to make something feel better than it strictly needed to.
What Apple platforms still teach me
I spend a lot of time around Swift, SwiftUI, and tvOS, and that shapes my taste even when I am building for the web. I like interfaces that feel calm, readable, and precise.
Apple platforms reward care. Small changes in spacing, motion, focus behavior, or state handling can change how trustworthy a product feels. I like bringing that same attitude into side projects.
How I like to build for fun
I prefer direct ideas over elaborate roadmaps. Start with one mechanic, one screen, or one useful behavior. Keep the scope small enough that attention can go into feel instead of project management.
Discipline still matters here. If I am going to share something, I want it to feel considered. Small projects deserve editing too.