Match the mode to the job
| Need | Test | A result that does not answer the question |
|---|---|---|
| A two-person conversation | Both people speaking, with readable results | A demonstration of typed text only. |
| A menu or sign | The actual image input workflow | A voice-only demo. |
| An address | The name, numbers and script remain intact | A fluent sentence that changes the destination. |
| Use without a connection | The exact mode after disconnecting | A downloaded text pack without testing voice. |
| A phrase sheet | The saved cards reopen and remain legible | A promise of unlimited live translation. |
Run the same small test in each candidate
Use three original practice cases: a destination with a building number, a price with a currency, and a changed date. Keep the sentences and conditions consistent across candidates. Record the phone model, operating system, app version, language direction, connection and input mode. Do not put private bookings or actual payment details in a comparison test.
Check the recognised source text before judging the translation. If the microphone heard the wrong number, record a speech-recognition problem separately from the translated wording. Ask a suitably fluent reviewer to evaluate meaning; the English author alone cannot certify both directions.
Use outcomes rather than a single star score
| Outcome | Record |
|---|---|
| Completed | Both people confirmed the intended detail. |
| Needed repair | The detail was corrected after a repeat, edit or written note. |
| Failed | The task could not be completed or a key detail changed. |
| Unknown | The feature was unavailable, not tested or could not be independently reviewed. |
A fast answer with the wrong date is not a success. A slower exchange that exposes and repairs the error can be more useful. Keep price, sign-in requirements and privacy terms as separate comparisons checked on the date you test.
What this guide can and cannot rank
We have not run a current comparative device trial for the apps discussed by other publishers, so this page does not declare a winner. Inside Kyoto’s Japanese travel comparison is an example of publishing concrete tasks; its device scope and dates need checking before applying its findings to your phone.
For a language-specific checklist see Japanese app selection. Test connectivity with the offline readiness planner. Check Pocket’s public support information for release status rather than treating this guide as a feature promise.
Sources and scope
Practical examples and checklists on this page are editorial exercises, not recordings, measured app results or claims about a currently released feature.