The technical complexity of operations on the TON blockchain means users often wait several minutes for a transaction to execute — depending on the operation type. Anxious about losing their funds, they flood the support team with tickets. After the global release of STON.fi V2.0, user numbers spiked — and so did the support load.

Processing modal

Before jumping into wireframes, we map every transaction in the product — 64+ statuses, 16 operation types, and 3 distinct UI components. Everything needs a unified copy structure and logic aligned with the backend.

We define the status copy for every operation type on the client side.

After syncing with engineering and signing off on the matrix, we move to the solution.

First decision: eliminate the persistent processing modal. Once a user confirms a transaction in their wallet, the modal collapses — a snackbar takes its place showing the live status. The full on-chain journey is accessible with a single tap.

This way, we stop blocking users with a modal overlay.

As an educational touchpoint, we introduce granular, clear transaction statuses — giving users the context they need to understand how the blockchain works.

Reviewing the full user flow, we find that the confirmation screen and the status screen carry the same transaction data — but look completely different.

We unify the visual structure, standardize the layout, and introduce new components built to the design system spec.

We assemble the complete user flow — all components with variables and auto-layout, all edge cases and empty states, full specs. Alongside, I run all in-product copy through AI tools to check grammar and punctuation. Then we run a dedicated demo session for a smooth engineering handoff.