Understand the entry point you are using
You may open Unihongo in a regular tab or from an installed app-style entry. Both are ways to reach the learning service. The presence of a separate window does not mean you must manage it like a traditional store-distributed package. Use the real site and the browser’s available controls when checking how you are accessing it.
At the same time, avoid treating “web based” as a guarantee that an already-open page immediately reflects every new change. A learning session has its own state, and browser resources may be managed separately. Verify what the current page actually does before making conclusions from its icon or window frame.
Preserve the work that a refresh could interrupt
An unsent diary entry, a sentence you are editing, or an in-progress activity deserves attention before you reload. Finish the action if practical, or preserve the text in a safe place you control. Checking a release is easier when you are not also trying to reconstruct an answer you accidentally discarded.
| Before refreshing | Reason |
|---|---|
| Check unsent text | An input field may contain work that was never submitted. |
| Confirm the last completed action | Reopening is not evidence that a learning task was completed. |
| Note the next step | You can resume with a clear purpose after checking the page. |
Reopen with a connection and inspect one feature
Confirm connectivity, then reopen the installed entry or reload the browser page. Check the account and the specific feature that seemed different. A narrow check is more useful than browsing randomly for signs of change. If a correction or layout now appears as expected, return to the task rather than continuing to reset settings unnecessarily.
Report persistent differences with useful context
If the result remains unexpected, record the device type, browser, page address, and what you did. Explain the observed behavior and the expected behavior separately. This helps distinguish a missing option from a connection failure, account access issue, or rendering problem. Avoid including private learner messages or sensitive account details in a public report.
Resume the learning thread deliberately
Tell Mocchi which activity you completed and what you planned next. A reload does not teach a word, submit a draft, or complete a study task by itself. Keeping the next action explicit prevents a small technical check from consuming the whole visit. The goal is a stable return to useful practice with your work and learning context intact.