
Article · Choco
UX error handling at Choco
The guidelines we put together for the Choco ordering apps: how we show errors, success and loading states so people always know what happened and what to do next.
Good error handling, success messaging and loading states quietly decide how a product feels. They tell people the status of their action, whether something went wrong and what to expect next. These guidelines were put together for the ordering apps at Choco, so that every squad would handle these moments the same way, in design and in code.
They are a starting point, not a rulebook. Some of the flows below were proposals at the time, and every team should test and iterate on its own flows and update the guidelines when it learns something new.
Key principles
- Clarity. Messages should be clear, concise and free of technical jargon.
- Relevance. Show information that relates to the action and its context, so people understand what went wrong and how to fix it.
- Timing. Show errors as soon as they happen and success as soon as a task is done. Show a loading state before a task takes too long, so people know the system is still working.
- Visibility. Messages should be easy to notice, with a clear call to action where it helps.
- Feedback. Every action gets feedback, failed or successful. It builds understanding of the system and a sense of control.
- Consistency. The same design and tone everywhere, so people know what to expect.
- Usability. People should be able to act on a message quickly and easily.
Copywriting: default and specific
Most messages come in two kinds of copy.
Default copy is standardized and covers most actions: "Loading…", "Changes saved.", "Unexpected issue. Could not save changes." It keeps the experience consistent and is quick to implement.
The downside is that default copy alone is too generic. It doesn't explain the problem, so people are left guessing what went wrong and how to fix it. That leads to confusion, frustration and less trust, and often to extra steps or support requests.
Specific copy is written for a particular action. It explains what went wrong and how to resolve it: an unavailable product, a missing delivery date, a delivery date in the past, an amount below the minimum order, an outdated cart in a team order. The goal is to balance the two: default copy as the safety net, specific copy wherever the system can tell us more.
How we show errors
Full screen errors
We use two default full screen states: no internet connection, and API or timeout errors.
- Do: show a full screen error only when a page is opening. The skeleton loader is followed by the full screen error.
- Avoid: full screen errors while someone is working on a page that has already loaded. Use a toast instead.
Toast errors
The same two defaults exist as toasts:
- No internet: "No internet. Please check your connection and try again." with a Retry action.
- API or timeout: "Something went wrong. Please try again." with a Retry action.
On top of these come the specific toasts for single orders, team orders and order editing.
- Do: use toasts when an action is performed on a screen where everything has loaded.
- Do: always use specific messages when the technical capabilities allow it.
- Do: use pre-approved copy, or get it approved by the product designer and copywriter.
- Avoid: skeleton loading together with toasts. The page is already loaded, unless certain elements really need to transform.
Patterns by flow
To keep things consistent we collected repeatable patterns. Following them standardizes not only copy and style, but also the implementation.
1. Toast loader (the default case). The person performs an action, a loading toast appears, then success or an error. An error allows two retries and finally the option to cancel. Example: creating a category in an order guide.
2. Button loading. When there is a prominent call to action, a loader replaces the button label. No toast loader is needed. Example: adding a team member to a business.
3. Several actions on one page. While the primary action is loading, the other actions on the page are disabled or hidden, and they come back once it finishes. Example: starting a team order. What we learned: the toast should not offer a retry here, and it should never cover the main call to action.
4. Sorting products. This one is different. The new order is stored locally and saved only when the person taps Done or takes another action, so it doesn't follow the usual trigger, loading, result pattern. That creates a trap: someone reorders products, then taps to edit a category instead of Done. The category change succeeds or fails, but the new product order is never saved, and nobody notices. The same can happen when renaming a category, renaming a product or deleting one. Our options: show a full screen error when there is no internet before entering edit mode, auto save live edits after a short time, or add an explicit save step, which would change the experience completely.
5. Default modals. For no internet, link straight to the device settings when possible, and mention airplane mode, since it is a common cause. The same details help in full screen errors and toasts too, as long as the toast still fits on the screen.
Why it matters
None of this is glamorous, and that is the point. When error handling is consistent, people stop noticing it. They just recover and keep ordering.