I created this post for the purposes of entering the Gemini Live Agent Challenge.
Today I tried to make our app feel like one experience instead of separate features taped together.
What I Executed
- Built and stitched the full path: Go backend scaffold + Next.js renderer + WebSocket proxy + Live API tool loop.
- Added onboarding pieces end-to-end: OAuth, YouTube analysis, voice matching, and state transition.
- Implemented reunion experience pieces: affective dialog rules, memory recall, BGM controls, and image consistency.
- Finished the “after” flow: album generation + share page.
- Added test/deploy confidence: unit + E2E coverage, Cloud Run config, README updates.
Evaluation Process
- Worked in small issue-sized PRs and merged in sequence.
- Verified through tests/build/static checks and CI passes per PR.
- Rechecked the user journey as one story (onboarding -> reunion -> album), not just isolated modules.
Failed Attempts
- A few “quick fixes” for real-time behavior made things worse before they got better.
- I had to back out and simplify some flow assumptions when timing issues appeared.
- I tried to move too fast in a couple spots; CI immediately exposed fragile edges.
Feelings
The most satisfying part was seeing the flow finally feel coherent.
The hardest part was accepting that real-time polish is never a one-shot win.
Today's Picks
- Result pick: first full run where onboarding -> reunion -> album felt connected.
- Process pick: ship small, verify, merge, repeat.
Closing Question
When you're building real-time features, what catches more bugs for you: automated tests or flow-based manual checks?
Top comments (0)