A translated string can be accurate and still make an interface difficult to use. Longer labels get clipped, buttons wrap badly, dates look wrong, and a right-to-left screen can expose layout assumptions that were invisible in English. A visual checking tool could visit the same application screens in several languages and compare the results. Developers would get screenshots of possible problems, with the affected text and route attached. A practical first version could detect overflow and untranslated strings on a defined set of pages. Teams would review findings and mark intentional differences, keeping the tool focused on visible issues instead of treating every variation as a bug.
Loading problems…
What should be built next?
Real problems, backed by people who want them solved.
