Archive#

This is where I collect projects I once launched via an app store (e.g., Google Play / the App Store) or on the web, but later took down or shut down, as well as projects I built with the intention of launching, but ultimately decided not to ship or put on hold. It’s not limited to Android apps for Google Play—this can also include iOS apps, web services, and other formats. Rather than keeping only “success stories” as a portfolio, I wanted a more honest place to preserve the trial-and-error and the decisions behind building.

Building an app isn’t just about writing code. It includes planning what to build, designing the UX flow, making technical choices during development, preparing a release and store listing, responding to user feedback during operations, and deciding at some point whether to keep going or stop. And often, the biggest learning comes from the stopping process—why things didn’t go as expected, which assumptions were wrong, what was missing, and what should have been validated earlier.

I keep this archive for two reasons. First, it’s a record for myself. Over time, the reasons behind a failure become blurry and only a vague “do better next time” remains. But if I preserve the context and the reasoning, it becomes a much more practical reference point when I face similar decisions again. Second, I hope it can help someone else. Success stories are useful, but many real-world problems are closer to “why it stopped.” For someone going through similar 고민, these failure cases might offer more direct hints.

Whenever possible, I try to include:

• Why I started (the problem / hypothesis)
• How I tried to solve it (core features, MVP scope)
• Technical/architecture/design choices and why
• Data and feedback observed during launch/operations (when available)
• Why it was paused/retired, and what I’d do differently now

Even without a finished outcome, the process becomes an asset. I hope the records collected here become material for a future restart—and a small guide for someone else.