Skip to content

Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy

Translation live preview
All projects

Translation

Show a simple English-Thai lookup flow before choosing a real translation service.

Serving English and Thai readers means translating content, and per-call translation APIs get expensive.

Tech Domain · Book Dev|Published|Evidence: Prototype|Next.js, TypeScript

A public prototype demonstrates the interaction; scope and data are intentionally limited.

Case Study

Before

Bilingual content needs a translation step, and paid machine-translation APIs cost money per call.

After

Translation on the App shell: type the mapped words and see them swapped between English and Thai; unknown words pass through unchanged and are listed.

How it's solved

Built a language desk that maps words through an eight-word English-Thai dictionary in the browser, with an EN to TH / TH to EN switch, a swap of direction and text, a list of unknown words, and tap-to-add chips for the words it knows.

Trade-offs

Dictionary lookup only: no translation API, translation memory or batch processing.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev