Let’s talk ↗
← Projects
Product design / CASE STUDY

Advin

Interface design for a manufacturing marketplace.

My roleDesign of the presented screens
TOOLS / PRACTICEFigma · UX/UI · Marketplace
Case formatJourneys · screens · UI kit
INTERFACE DESIGN

Designed the interface

My contribution covers the design of the presented screens and journeys.

01UX02UI03SYSTEM
In this project
  • Three roles
  • Order journeys
  • UI kit & states
AdvinAdvinAdvin
Advin / Product design

The challenge

Design a clear interface for discovering services and managing orders.

These screens represent my contribution. Other parts of the live product may have been designed by the wider team.

DESIGN PROCESS / SOURCE MATERIAL

This case is grounded in the project’s original flows, design versions and UI kit. Open any material at full size. The chapter order explains how decisions connect; interviews or testing are not claimed without supporting source material.

01 / PRODUCT CONTEXT

Three roles, different paths through one order

Customers create a brief and choose a proposal. Designers work with the brief, concepts and files. Providers turn approved artwork into production and delivery. Separate flows and interfaces connect these tasks through a shared order.

ROLE

Customer

Find a service → configure it → compare proposals

ROLE

Designer

Choose a brief → propose concepts → hand over files

ROLE

Provider

Respond → produce → confirm the result

02 / INFORMATION ARCHITECTURE

Start with sections and relationships

The source retains current and new customer sitemaps. They show the relationship between catalog, orders, messaging and profile, and allow the versions to be compared before examining individual screens.

Sitemap / current
Sitemap / new
03 / USER FLOWS

Connected journeys across the screens

The flows document actions and decision points for each role: order creation and tracking for customers, briefs and approval for designers, and production and completion for providers. Expand each source flow to inspect it.

Customer journey↗
Customer journey
Designer journey↗
Designer journey
Provider journey↗
Provider journey
04 / DESIGN EXPLORATION

Comparing versions in the source file

An exploratory homepage lives on another source page, while the desktop design is on the Design page. The comparison shows different arrangements of catalog, work examples and navigation. These are interface versions, not a claimed A/B-test result.

Version on a separate page
Desktop version / Design page
05 / DESIGN SYSTEM

The design system, section by section

The Advin source UI kit defines role colors, a Golos Text scale, buttons, inputs, cards, badges and navigation. The original boards and 20 source SVG icons connect three role-specific workspaces.

Choose a section. Open a board to inspect it at full size.

01

Colors for three roles

Colors for three roles
02

Golos Text and type scale

Golos Text and type scale
03

Buttons and states

Buttons and states
04

Fields and validation

Fields and validation
05

Chips and tags

Chips and tags
06

Badges and statuses

Badges and statuses
07

Cards for different entities

Cards for different entities
08

Navigation

Navigation
09

Progress, messages and states

Progress, messages and states
10

Original SVG icons / 20 examples

Icon 1
Icon 2
Icon 3
Icon 4
Icon 5
Icon 6
Icon 7
Icon 8
Icon 9
Icon 10
Icon 11
Icon 12
Icon 13
Icon 14
Icon 15
Icon 16
Icon 17
Icon 18
Icon 19
Icon 20
06 / CUSTOMER JOURNEY

From finding a service to tracking the order

The journey starts with service discovery and product parameters, then moves through artwork preparation, brief review and proposals. Messaging and order states continue after a provider is chosen.

Home and categories
Service search
Artwork preparation
Product configuration
Brief review
Provider proposals
Order conversation
Order in progress
Completed order
07 / DESIGNER JOURNEY

Briefs, concepts and handover

Designers have a brief feed and detailed requirements. Concepts carry approval states, and file transfer is a separate step with deliverable requirements. The design covers approval and handover as well as discovery.

Brief feed
Brief details
Concepts and states
File handover
08 / PRODUCTION JOURNEY

Production has its own interface

Providers respond to orders, manage production, document results with photographs and arrange delivery. The content changes at each step while the order and role context remain consistent.

Order feed
Production
Photo documentation
Delivery
09 / DESKTOP ADAPTATION

The same tasks on a larger screen

Desktop layouts redistribute space into persistent navigation, a working area and supporting information. The following show customer discovery, designer concepts and provider production.

Customer / desktop
Designer / desktop
Provider / desktop
10 / STATES & HANDOVER

Response, rejection, progress and completion

The project includes a rejected response, file-delivery requirements and in-progress and completed orders. Badges, messages, indicators and control variants in the UI kit support these distinctions.

Response rejected
File-set readiness
Order completion
VISUAL LANGUAGE

The project’s character

#10a64a
#f0fbf4
#18251d
01Figma02UX/UI03Marketplace
DELIVERABLE

The outcome

Mobile screens, navigation and interaction flows. My contribution is the screen design in the linked Figma file.

Next projectDaryn AI ↗
LET’S TALK

Let’s discuss your idea.

Message me on WhatsApp about your project or a job opportunity.

Message on WhatsApp+7 708 903 43 49