UX/UI Design - Mobile App & Web Portal

Freelance UX/UI Designer – Credentis (3–4 Weeks, Figma)

Project: Credentis – Digital ID and Workforce Verification Platform
Engagement: 3–4 weeks (fixed-scope sprint)
Deliverable: Production-ready Figma design system + key flows
Platforms: Web dashboard (React) + Mobile wallet (Flutter)

About Credentis

Credentis is a trust and compliance platform for verified projects. Users hold decentralised identities (DIDs) and verifiable credentials, grant category-scoped consent, and participate in verified project workflows.

There are two complementary clients under one brand:

Mobile (Flutter) – Identity wallet for professionals and organisations: create/restore identity, manage credentials, accept project invites, and control consent.

Web (React) – Operations dashboard for client organisations, partners, and managers: projects, PQQ templates, partner onboarding, workforce, and compliance.

Core journey: Prove who you are → hold credentials → consent to share data → participate in a verified project.

There is no existing Figma. The current visual source of truth is live CSS tokens in the web app and a partial Flutter theme. Brand colours already align (teal accent #1F6B5C, ink #14231F, sage surface #F1F5F3); web uses Bricolage Grotesque + Source Sans 3; mobile still uses default Material fonts.

What We Need

We’re looking for an experienced product/UX/UI designer to establish a shared design system in Figma and design priority end-to-end flows for both web and mobile, including light and dark themes, so engineering can implement without inventing UX.

You’ll clarify the role-based information architecture (wallet vs dashboard) while keeping one brand language, and replace stub/placeholder UX (especially mobile capture/KYC and dense web ops screens) with production-ready patterns.

Scope (3–4 Week Sprint)

Week 1 – Foundation

Audit live apps (or walkthrough with product/engineering)

Figma foundation: colour, type, spacing, elevation, status colours, icon direction

Dark mode token set paired with light (surfaces, text, borders, accent, status); contrast-safe pairs; theme-switch pattern

Core components: buttons, inputs, forms, tabs, tables, pills/badges, nav (web + mobile), empty/loading/error states – with light/dark variants

Cross-platform rules: what is shared vs platform-native (Material/iOS patterns on mobile; dense ops layout on web); how dark mode maps to Flutter Material 3 / web CSS variables

Week 2 – Mobile Critical Path

Onboarding + trust UX (backup phrase, remove identity)

Capture/KYC flows designed as real camera/OCR/liveness UX (permissions, retry, failure)

Wallet shell + credentials + consent decision patterns

Week 3 – Web Critical Path

Project detail IA (reduce 7-tab cognitive load: grouping, defaults, role-aware views)

Partner PQQ completion + review

PQQ template authoring (nested forms, clarity over density)

Onboarding dashboard for mixed partner/manager tasks

Week 4 – Continuity, Polish, Handoff

Web ↔ mobile identity handoff (register with mobile-provisioned identity)

Empty states, status taxonomy, responsive/ops breakpoints for web tables/forms

Dark mode applied to priority mobile and web flows (high-fi for key screens; component library covers the rest)

Final Figma organisation, annotations, component variants, open questions log

Walkthrough with engineering + product; revision pass

Audiences & Flows to Cover

Mobile – Holder

Splash → welcome → create identity (person vs org) → registration (passport / selfie / RTW – currently stubbed) → recovery phrase backup → attach login → sign-in

Wallet shell (4 tabs): Wallet, Credentials, Projects, Consent

Credential list + upload/scan

Project invitation → apply → participation detail

Consent request → approve/reject → active grants → audit

Web – Org / Partner

Login / register (identity ID handoff from mobile)

Identity profile

Projects list → create → project detail hub (Overview, PQQ templates, Partner onboarding, Delegations, Invitations, Participations, Compliance)

PQQ template authoring (+ import affordance)

Partner onboarding fill + review/approve

Cross-project onboarding task dashboard

Workforce invite / review patterns; humanised statuses (not raw API enums)

Deliverables

Figma file – Shared library + Web + Mobile pages; named frames; auto-layout preferred

Design system – Tokens mapped to existing Credentis colours/fonts; light + dark semantic tokens; component set with variants/states

Key flows – Clickable prototypes for: mobile onboarding→wallet; consent approve; web project create→partner onboarding→review

Screen set – High-fidelity for priority flows (light + dark for those screens); mid-fi acceptable for secondary states if time-boxed

Dark mode – Full token pairs; theme switch pattern; dark variants for core components; priority-flow screens in both themes

Handoff notes – Specs for spacing/type; platform notes (Flutter Material 3 vs web custom CSS / CSS variables); file/page map

Status & role taxonomy – Proposed human labels for identity/credential/consent/participation/onboarding states

Assumptions & open questions – Short doc page in Figma or linked markdown

Acceptance: Product/engineering can implement Weeks 2–3 flows without inventing major layout or interaction patterns; design system covers the components used in those flows (including light/dark); Figma is structured for reuse beyond this engagement.

Constraints & Inputs You’ll Receive

Access to staging or local web + mobile builds (or recorded walkthrough)

API/domain glossary (identity types, project roles, consent categories, status machines)

Existing token values from web src/index.css / mobile lib/theme/credentis_theme.dart

Product owner for role/compliance questions; engineering for feasibility of capture/OCR stubs becoming real

Tech context (for handoff awareness, not for you to implement): Web = React/Vite/custom CSS; Mobile = Flutter Material 3; both talk only to the API gateway.

Success Criteria

One coherent Credentis visual language across web and mobile, in light and dark

Mobile onboarding/capture and web project/PQQ/partner flows are design-complete for engineering

UUID-first and raw-enum UX have proposed human alternatives

Dark mode tokens and priority-flow screens are handoff-ready (not every secondary state required in dark if time-boxed)

Design system is small enough to ship in 3–4 weeks and extensible afterward

Ideal Freelancer Profile

Strong portfolio of design systems and multi-platform products (web + mobile)

Experience with identity, KYC, consent, or compliance products is a plus

Comfortable working from live code tokens and collaborating closely with engineering

Fluent in Figma (auto-layout, variants, tokens, prototyping)

Able to work in a 3–4 week fixed sprint with clear milestones

How to Apply

Please share:

A short intro (2–3 sentences) on relevant experience

1–2 case studies showing design system + flow work (web + mobile)

Your availability and weekly rate for a 3–4 week engagement

We’re aiming to start pretty much immediately and move quickly through a short paid discovery if needed.