Do not collapse every polite form into “formal”
Busuu’s lesson by Korean teacher Keehwan Kim distinguishes formal, polite and casual greetings. Its everyday polite example differs from the very formal and casual examples. That makes the participant relationship useful context for a translation test; a single “hello” result cannot certify the appropriate wording for every interaction.
For an ordinary travel exercise, specify an unfamiliar traveller and a staff member. For a separate friends exercise, say that the participants know each other well. Ask a fluent reviewer to assess the result for that scenario. Do not ask an app to infer age, status or intimacy from a name or appearance.
Test context without publishing unchecked Korean dialogue
| English prompt | Context | Reviewer’s check |
|---|---|---|
| Excuse me, can you help me find this place? | Unfamiliar staff member | The request is polite and preserves the destination. |
| Can you say that again? | The traveller did not understand a reply | It requests a repeat rather than claiming agreement. |
| We need two tickets, not three. | A quantity is being corrected | The correction and negative survive. |
These are authored English prompts. This page does not supply reviewed Korean translations for them or claim native-speaker certification. A machine back-translation can reveal a problem but cannot replace the reviewer.
Keep the original Hangul name with the map
Use the venue’s own Hangul name and address when supplied. Keep any romanized version separately labelled and check that both identify the same place. If you cannot read the script, compare it visually with the source instead of typing an approximation from memory. Keep building numbers and entrances as their own details.
A readable source card also helps when the microphone captures an unfamiliar place name incorrectly. It gives the other participant something concrete to point to while resolving the mismatch.
Check the answer and final detail
Test the Korean speaker’s reply, not only the traveller’s English request. Record the input mode and whether the source transcript can be checked. Finish by showing the final quantity, name or time so the other person can correct it. Use the practice worksheet to record a completed, repaired, unresolved or unknown outcome; do not infer a language accuracy percentage from a few examples.
Sources and testing scope
This is an app-agnostic preparation checklist. The practice cases are editorial exercises, not measured app output, a feature availability claim or a native-speaker review. Check any product’s current release and the exact language direction before using it.
Use the app test sheet to record results and the offline readiness planner for connection checks. Pocket’s current public product information is on Support.