Pixel Penny.

Pixel Penny was a mobile app I built as a solo side-project - a small, opinionated tool I thought could fit into people's daily routine. I had a clear picture of the product in my head and I was excited to ship it.

A working React Native app: onboarding flow, core feature, local persistence, polished UI. It was functional end-to-end and I could hand it to a friend and they'd know what to do. By engineering standards it was ready. By product standards it wasn't.

Three compounding reasons, in order of honesty:

1. 01I never validated whether anyone actually wanted it. I skipped the awkward part - talking to potential users, running a waitlist, testing the problem in public -and went straight to building, because building is the part I'm comfortable with.
2. 02I didn't market it. I put the app out and waited, as if "shipping" and "distributing" were the same thing. They're not. Without a distribution channel, even a good product is invisible.
3. 03The space was already crowded with well-funded, better-marketed competitors. I didn't have a sharp enough angle, a 10× feature, or a specific audience that the incumbents weren't serving. Being "another" option in a solved category is the fastest way to zero.

The combination was fatal: no validation meant I was building on a hunch, no marketing meant no signal to correct it, and no differentiation meant no reason for anyone to switch. So I stopped.

• Shipping ≠ launching. The work I'm good at - design, engineering, polish - is maybe 40% of what it takes to get a product to users. The other 60% is distribution, positioning, and conversation. I had been treating that 60% as optional.
• Validate before you build, not after. A landing page with a waitlist takes a weekend. An app takes months. If I can't get 50 sign-ups for a landing page, the app isn't going to do better.
• Pick fights I can win. Going head-to-head with well-funded incumbents is a losing strategy for a solo dev. The right angle is a narrow audience, an underserved use case, or a product shape the big players can't or won't build.
• Sunk cost is not a reason to continue. The code was good. The decision to stop was still correct. Keeping a project alive out of attachment costs more than the write-off.

Probably not in its current form - the category is still crowded and I don't have a new angle. But the muscle I built doing it (RN, offline-first storage, onboarding UX) now lives inside Recappy, which is finding traction. So Pixel Penny didn't ship, but it wasn't wasted - it was tuition.