

PROJECT
SYNC- AI Workflow app
ROLE
Product Designer · UX · AI Product Development
INDUSTRY
Architecture & Interior Design
YEAR
2026
INDUSTRY
Developed as the capstone project for the Google AI Professional Certificate on Coursera, using Google AI Studio to take the concept from problem framing and product design to a working AI-powered web application.
↳
(VISUAL FOUNDATION)
Calm at a glance. Clear when it matters.
I used quiet neutral surfaces and consistent cards to keep dense project information manageable. Stable patterns reduce relearning, while stronger emphasis is reserved for urgent work. The aim is to make priorities clear without making the entire workspace feel urgent.
A stable workspace
Consistent navigation and aligned cards keep the surrounding interface familiar.
Visible priorities
Overdue releases carry stronger colour, explicit timing, and a direct action.
Connected decisions
Drawing identity, ownership, dates, and next steps stay together.
Overview exhibit

(COLOUR SYSTEM)
Every colour has a job.
Green identifies primary actions, blue orients time-based information, and amber and red distinguish approaching and missed deadlines. Colour communicates meaning, not decoration. Labels and milestone shapes reinforce those signals so priorities can be interpreted without relying on colour alone.
#087F5BBrand · primary action
Release drawing#2563EBInformation · Today
Today, 4 Nov#F59E0BApproaching deadline
Due soon#DC2626Missed release deadline
Overdue#F2F5F4Workspace canvas#FFFFFFContent surface#C8D3CCStructure & borders#172B23Primary textColour is a supporting cue: “Overdue” remains readable as a label, and the timeline uses different milestone shapes. Green’s brand and status roles are distinguished by their labels and context.
(TYPOGRAPHY)
Readable detail. Deliberate hierarchy.
DM Sans gives drawing names, dates, and controls a consistent visual voice. A 18px primary / 14px supporting scale separates key decisions from metadata without excessive type variation. The intended result is readable detail and a predictable scanning order.
abcdefghijklmnopqrstuvwxyz
0123456789 · → / +
MON-002 · Rohan Mehta
Identity, owner, and datesMON-002 · Monsoon Pavilion
Release overdue by 2 days
(COMPONENTS)
One system. Familiar interactions.
Repeated buttons, fields, and status patterns create one interaction language across the workspace. A clear primary action, visible focus, and explicit disabled states communicate what is available. The aim is to reduce uncertainty as users move between tasks.
One prominent action, with quieter alternatives. A visible focus ring supports keyboard navigation.
Persistent labels give context; clear validation explains what needs correction. Preview fields only; no product data is submitted.
Short, consistent terms repeat across the ledger, timeline, and project summaries.
Outline icons support scanning. Important actions retain a text label.
(LAYOUT & HIERARCHY)
The task changes. The hierarchy follows.
The overview is action-first; the timeline is date-first. Each layout gives more space to the information its task depends on, while grouping owners, dates, and actions with their drawing. This aims to shorten the path from scanning to a relevant decision.
Metrics establish context; priority drawing releases appear before project imagery.
Dates become the main content; overview details become supporting context.

A stable left edge connects headings, cards, and detailed rows.
Related dates, owners, and actions share the same drawing row.
The timeline guide expands when needed; drawing details open in context.
Project scanning

Date-led hierarchy

(KEY WORKFLOWS)
From noticing a risk to taking action.
Each journey follows notice → understand → act, keeping drawing identity and timing in context. Resetting approval after a new revision avoids carrying an earlier decision into changed work. The intended outcome is clearer handoffs and fewer ambiguities about the next step.

Know what needs attention and act on the right revision.
The drawing stays connected to its project, owner, deadline, and next action. A new revision resets approval.
Explore this workflowDetailed drawing ledger

(MOTION & RESPONSIVE)
Measured motion. Flexible composition.
Motion explains state; responsive layout preserves meaning. A gentle stagger connects changes, while explicit mobile date cards retain timing when a calendar becomes too compressed. Reduced-motion support keeps the same information available without animation. The aim is continuity across states and screen sizes.
Flow with purpose.
600ms entrance · 100–260ms stagger.
Reduced-motion preferences disable transitions.
Replay the three-step release sequence.
The shared date axis makes drawing deadlines comparable.
Roof truss connection details
2 NovSite starts
9 Nov
Compact composition keeps dates explicit and readable.
(ITERATION & LIVE WEBSITE)
Refined through review. Ready to explore.
The comparison makes the reasoning behind stronger contrast, explicit milestones, and separate dashboard modes visible. Refinement is demonstrated; improvement still needs validation. Testing representative release tasks should reveal completion issues, misunderstandings, and navigation problems before better usability is claimed.

Brighter status colours and darker text make urgency more visible.
Named milestones, an explicit date axis, and a Today marker replace ambiguous bars.
The calendar comes first in Release timeline; Overview keeps the broader practice view.
Go beyond the frames.
Explore the dashboard, drawing ledger, and stage planner in the final Codex build.
Explore the hosted final build. Records remain in this browser; external delivery and a shared backend are not connected.Next validation: observe representative users finding an overdue release, interpreting the timeline, and preparing a drawing. Compare task completion, misunderstandings, and navigation paths before making outcome claims.


