Kondesk Mobile

Process - Interviews → IA → wireframes → polish

I led IA and user flows on top of the Kondesk CRM concept. To ground every decision, I debriefed with agents and studied live cases.
A clear pattern emerged: request → wait → clear.

The app mirrors that flow. Tabs act as places for stable navigation, while cards act as actions that surface just in time and clear when completed.
CRM events map one-to-one with UI updates, keeping the screen always in sync with the current task.

I designed the system around four core principles:
Stable wayfinding kept navigation shallow and predictable.
Task-first disclosure revealed the next action just when needed.
One-hand ergonomics ensured thumb-zone reach even with long labels.
Scalability allowed new work to start as cards and graduate into tabs naturally.

In pilot testing, the approach worked.
Applicants submitted fewer duplicates and sent fewer status-check messages.
Three action cards consistently beat five for time-to-first-action and fewer mis-taps.
Navigation logs showed more returns to Home with pinned tabs and fewer dead ends.
Accessibility testing confirmed larger tap targets and smoother scrolling in long-label locales.

Dynamic Home (the do-board):

I designed Home as a live to-do board, not a feed. It displays up to three small cards (Upload, Pay, and Join), each paired with a clear chip like Due today and a service tag such as Study Visa.

Users can tap, complete the short flow, and return to Home, where the card automatically updates or clears.

Agents can approve or request fixes, and notifications open the exact card so users never have to search for the next step.

Bottom tab bar:

I pinned Home and the highest-frequency tabs while allowing the rail to scroll horizontally for the rest.

A fixed bar couldn’t hold long labels or multiple peers, so this layout keeps everything first-order and thumb-reachable.

Less-used areas (Docs, Payments, Calendar, and Add-ons) live inside a “More” drawer, surfacing automatically on Home when relevant.

How the flows evolved, from wireframes to usability passes

Documents

Evolved into a guided capture flow with scan, crop, compress, and upload steps.
If the network drops, an Outbox queues retries automatically.
Status is simple: Submitted → Under review → Verified / Needs fix.

Payments

Now happen in context with invoice, pay, and receipt screens all in one place.
Plain-language errors and clear Retry or Change method options remove friction.
If documents are pending, the card marks Must pay first.

Classes

One tap to Join (online) or View location (offline).
The Calendar manages reschedules within seconds, checking for conflicts and time zones automatically.

Agents

Act as a utility where users can call or message with history.
Approvals or fix requests automatically update the right cards on Home.

Across all flows, I designed empty, error, and offline states first, keeping the tone calm and the next step always visible.