Skip to main content
Back to the villageDONGGU’S FIELD NOTESDOTJARI
The workshop · selected work
PLACE
개인 프로젝트
ROLE
Full-Stack
STARTED
2026-04
★ Case 05 / 7Forward Deployed Engineer Donghyun Kang

Han River Social Dating App (Personal Product)

When code takes 5 minutes to write, deciding what to build takes days — a solo product engineer turned one Han River scene into a shipped product in 3 weeks.

개인 프로젝트Full-Stack2026.04
01.Discover

When code takes 5 minutes, the hard part is the decision.

I was eating chicken with my family at Ttukseom Han River when I noticed the next blanket over. Two guys in suits were asking to join. My wife and I cracked up. That scene was the start. The first product I built without a real user pain — I just thought the Han River picture was funny.

No persona analysis, no market research, no team meeting. I was the one who normally chants "MVP, MVP," and yet I could not stop myself. Pair matching or group matching — that was the decision that took the longest.

Cursor and Claude Code were always on, so I wrote code fast. In exchange I let the decisions go slow on purpose. In a workflow right after AI dropped the cost of code to zero, what a product engineer is left with is the decision.

Field notes

Note 01

Starting without user pain

One scene at the Han River was all there was. Zero personas, zero market research.

Note 02

I could not stop myself

The one who normally chants MVP was me — and that is the weight of deciding alone.

Note 03

Decisions took longer than the code

Code in 5 minutes; decisions across several days.

02.Build with AI

Slow on the decision, instant on the build — AI was not a tool, it was the cycle accelerator.

Decision 01

Drop pair matching

The decision I sat on the longest. Pair matching was too elaborate, not an MVP. The hardest part was that I — who normally chants MVP — could not tell myself to stop. That one decision turned into the core asset of the launch.

Decision 02

AI-first workflow (Cursor + Claude Code)

Code fast, decide slow. The risk of 5-minute code was that you could go 5 minutes in the wrong direction. I used AI as the cycle accelerator, not as a tool.

Decision 03

The weight of deciding alone

BeforeLooks fast from outside — no meetings, no reviews
AfterActually fast because the moment a decision lands, the hands move

tradeoffEven showing the work to my wife or a colleague does not move me unless the direction matches what I already want — both the limit and the weight of solo decisions.

Decision 04

Stack choice for shipping three platforms together

Flutter for iOS and Android, Next.js for web. Supabase cut backend infra cost and time. The thing that let one person carry three platforms at once was the stack choice itself.

03.Prove with metrics

Inside three weeks, the decisions compressed into shipped product.

Time to ship

3 weeks

2026.04.07 → 04.28

Team

Solo full-stack

Planning, design, dev, ops — all alone

Scope

3 platforms

iOS, Android, web shipped together

Ops

Daily auto-report

Han River events, social, competitor watch

What this case is really about
“A product engineer who, in an era where writing code is free, defines the direction of a product through decisions.”
Discover

A single scene at the Han River — finding user delight without an obvious user pain.

Define

Zero personas, zero market research. Took a single hypothesis as the definition.

Build

AI-first workflow paired with a stack that ships iOS, Android, and web at once.

Prove

Solo-shipped in three weeks; the live ops feedback loop is running.

Linked principlesAnswer-in-FieldTech-is-Means
App Showcase

Real screens, in production

What happens when product, design, dev, and ops all run through one pair of hands.

YeopJari Dotjari, find a seat on the map
YeopJari Dotjari, activity discovery
YeopJari Dotjari, seat-sharing detail
YeopJari Dotjari, seat-sharing chat
YeopJari Dotjari, create a seat-sharing post
YeopJari Dotjari, community