LiveSnaps

LiveSnaps was an Android app that let users send photos from their phone gallery to Snapchat as native snaps — bypassing a friction Snapchat itself didn't address. It hit a moment when the affiliate-marketing world was peaking on Snapchat, and people needed a way to reuse content without re-shooting it.

I built it solo, shipped it to the Play Store, monetized it with a subscription, and ran the whole loop — engineering, support, billing, refunds, growth. When the affiliate moment passed and Snapchat's own product changed, I made the call to discontinue rather than keep a flatlining service alive. That decision is part of the case study, not a footnote to it.

LiveSnaps generated $50K+ in gross subscription revenue worldwide over its life. That's the headline. The numbers I care about more, as an engineer:

• Built and shipped end-to-end by one person (me)
• Subscription billing wired and stable enough that refund disputes were a rounding error
• Globally distributed users — paid traffic from regions I'd never targeted directly
• Sunset on my terms, with users notified, before the product became a maintenance tax

Working at FlowGPT, I'm one engineer on a team building one slice of one product. LiveSnaps was the opposite — every decision was mine, every bug was mine, every customer email was mine. Three things stuck:

• The product is the support burden. Every UX decision has a downstream cost in messages you'll personally answer at 2am. I now look at every flow asking "who handles this when it goes wrong?"
• Shipping a paywall changes how you write code. When real money depends on a button, you stop hand-waving error states. I write more defensively because of LiveSnaps.
• Knowing when to stop is part of the job. Discontinuing a profitable-ish product because the moment had passed was harder than launching it. Not every piece of software deserves to live forever.