Mobile Workflow Experience

This project covered the full mobile app experience for Moxo workflows, including the assignee portal clients use to complete actions and the admin portal teams use to track progress.

Clients could enter from mobile web without downloading the app, open the app directly, or authenticate through email and an email code. The design needed to make the first step easy while still supporting more complex workflow visibility when needed.

Another constraint was product coexistence. New Flow and V10 lived inside the same mobile app, but the signed-in experience changed by account type. The design had to introduce the new workflow model without breaking expectations for existing V10 users.

Mobile workflow users move between two different needs. In one moment, a client needs to know exactly what action to complete. In another, they need to understand where they are in the larger process.

At the same time, the app had to support two product generations. New Flow introduced a different post-login structure and visual style, while V10 still needed to remain available for accounts using the older experience.

A single dense mobile layout would either hide progress or overload the current task. I framed the design around two modes of attention: focused action and process visibility.

New Flow was not a separate app. It shared the same mobile app with V10, and the experience after login depended on the user's account.

This made consistency more subtle than simply applying a new visual style everywhere. I had to consider where the new workflow language should appear, how the app should distinguish account contexts, and how to keep shared patterns stable across both experiences.

Spotlight View became the default assignee experience. Instead of showing the whole workflow first, it brings the client directly into the current visible action.

The visible action depends on the workflow setup and what the assignee is allowed to see. All action types can appear in this mode except automation, because automation does not require the client to take manual action.

Gallery View is not the default. Admins can configure it in the template when the client should see more of the workflow.

It shows only the actions visible to that client, organized by status: in progress, completed, and not started. Clients can tap an action to open its detail page and complete it when it becomes actionable.

I also designed the admin side of the mobile app. In the workspace, admins can check all action progress from a list, then open an action detail page to review status or follow up.

This made the mobile experience a connected system: clients could complete work from the assignee side, while admins could keep visibility into workflow progress from the management side.

Beyond the individual views, I treated the mobile app as a set of reusable workflow patterns. The same interaction logic needed to work across assignee and admin sides, and across New Flow and V10 account contexts.

The design was shipped and implemented by engineering. The final experience supported mobile workflow execution across assignee and admin sides, with Spotlight View for focused action and Gallery View for optional progress visibility.