Programming & Development
2
UPVOTE
dev.to

My Biggest Mistake: Why You Should i18n Your Next.js App From Day One (A Vibe Coding Survival Guide)

My Biggest Mistake: Why You Should i18n Your Next.js App From Day One I built a split-bill application called FAMI-KAN (originally for the Japanese market) using Next.js 15 App Router and Supabase. Since I built it mostly through "Vibe Coding" (coding iteratively with AI agents like Claude/Gemini), feature development was incredibly fast. I have absolutely zero professional programming experience, yet AI allowed me to build a fully functional product. I thought I was a genius. Then, X (Twitter) expanded its multilingual features. Suddenly, global traffic was a real possibility. I realized: If people from around the world click my app link from X and see only Japanese, my user journey is completely broken. So, I decided to translate my app into 8 languages. "It should be easy with AI, right?" I thought. I was dead wrong. Not building with i18n (next-intl) from Day 1 was the biggest mistake of this project. Even with the power of Vibe Coding, migrating an existing, monoli
DC

DEV Community

6d ago
2 0

Discussion

Your thoughts matter!

Your input is valuable—be the first to share it!

No comments yet.

Be the first to share your take and keep the conversation moving.

Join the conversation

Log in or sign up to add your comment and participate in the discussion!

Log In Sign Up

UPVOTERS

Community appreciation

See who found this content valuable and showed their support.

JA

Jamie Rodriguez

Jamie RodriguezUpvoted 5d ago51 comments · 372 shares
KA

Fashion Kavitha

Fashion KavithaUpvoted 6d ago0 comments · 22 shares

RELATED CONTENT

Continue exploring

Discover more content that aligns with your interests and this post.

dev.to
Why I split a single color across two ANSI slots

I spent several weeks reading Claude Code output for hours at a stretch and the default themes were wearing me out. Not because the syntax highlighting was wro…
Stefani

Stefani

2026-06-11 19:02
0
dev.to
Flowork Agent: Self-Hosted AI Agents in a Single Go Binary

Flowork Agent is a self-hosted operating system for AI agents distributed as a single Go binary— no Docker, no Python, no separate database. It's a practical a…
Stefani

Stefani

8h ago
0
dev.to
HTML in Canvas API

For years, web developers have had to make a tough architectural choice when building complex, highly-interactive visual applications on the web/ Should you le…
Original Siri

Original Siri

18h ago
0
dev.to
Am I Reinventing the Wheel? Building a Company's AI Brain

I've been working on a new project that I call a Company Brain. The idea is simple: Instead of having separate tools for support, sales, marketing, operation…
DC

DEV Community

1d ago
0
dev.to
Anonymization Strategies

Detection tells you where the PII is. Anonymization decides what to do about it. Presidio's anonymizer ships with five built-in operators, each suited for diff…
DC

DEV Community

1d ago
0
dev.to
Stop sending every AI coding request to the expensive model

AI coding tools are powerful. But they’re also wasteful. A tiny helper-function question does not need Claude Sonnet. A huge architecture review probably do…
TL

Thomas Lefevre

1d ago
0

Still curious?

See more related posts

Keep the inspiration flowing with fresh submissions and trending finds from the community.

View Latest