Senior UI/UX Designer to Polish Chat-Based Cannabis Product Info App (UI/UX only)
OVERVIEW
We built an internal web app (“Product Professor”) that helps budtenders quickly find accurate product info and recommend appropriate products. Core functionality works; we need a designer to add clarity, warmth, and craft across three screens:
Landing/query screen (text input + optional voice)
Loading state (processing)
Chat interface (answers, follow-ups, quick actions)
UI/UX only — no backend, LLM, or API work.
SCOPE OF WORK (UI/UX ONLY)
Heuristic audit and direction: identify hierarchy, spacing, contrast, and usability issues; propose quick wins and priorities.
Visual language: refine type scale, color (light/dark), spacing, elevation, and state styles to feel modern, calm, and expert.
Screen polish:
• Landing: input prominence, helper text, voice affordance, CTA hierarchy, brand lockup, responsive behavior.
• Loading: progress treatment (skeletons vs spinners), clear latency messaging.
• Chat: message layout, readable line length, timestamps, actions (copy / ask similar), empty/error/no-result states.
Microcopy: clear, compliant, human tone (no medical claims).
Interaction and motion: tasteful transitions for send/receive, loading, toasts; respect reduced-motion settings.
Design system in Figma: buttons, inputs, cards, chips, tabs, toasts, icons; variants and usage notes; tokenization for Tailwind/CSS variables.
Accessibility: AA contrast, focus states, keyboard navigation, screen-reader labels.
DELIVERABLES
Short UI/UX audit with prioritized recommendations.
Hi-fi mockups and a clickable Figma prototype for the three screens (light and dark).
Component library with states/variants and a token sheet (color, type, spacing, radii, shadows, motion).
Motion specs (Figma animations or short GIF/Lottie references).
Microcopy guide for system messages, loading, errors, and disclaimers.
Dev handoff: organized Figma, annotations/redlines, and a brief Loom walkthrough.
OUT OF SCOPE
Backend services, data/LLM configuration, authentication, analytics, or any server/API work.
WHAT WE WILL PROVIDE
Current screens and flows (landing, loading, chat) and product content.
Brand constraints (tone: calm, knowledgeable, trustworthy), logo, initial palette.
Design/engineering point of contact for quick feedback cycles.
Frontend context: Next.js + Tailwind via bolt.new (for token parity in Figma).
MUST-HAVES
Portfolio of shipped web apps (ideally chat/knowledge tools) showing polish and systems thinking.
Expert Figma skills (autolayout, variants, component properties, prototyping).
Strong interaction/motion sensibility and accessibility fundamentals.
Comfortable designing for Tailwind/design-token workflows.
NICE-TO-HAVES
Experience in regulated or retail environments; familiarity with cannabis retail workflows.
Light front-end literacy, iconography/illustration, Lottie/After Effects.
ENGAGEMENT
Timeline: 1-2 weeks
Budget: $700
Collaboration: async first; weekly design reviews; quick Looms for iteration.
HOW TO APPLY
Start your proposal with "professor" and include:
2–3 relevant web-app case studies (before→after preferred).
A one-paragraph week-one plan for our three screens.
A link/GIF to a micro-interaction you designed that improved clarity.
SUCCESS LOOKS LIKE
Cleaner hierarchy and faster comprehension on all three screens.
Chat feels confident and helpful with clear actions and friendly system states.
Cohesive visual/interaction language (light and dark) and a maintainable component library.
Smooth dev handoff with minimal ambiguity.
Apply Now
Apply Now
We built an internal web app (“Product Professor”) that helps budtenders quickly find accurate product info and recommend appropriate products. Core functionality works; we need a designer to add clarity, warmth, and craft across three screens:
Landing/query screen (text input + optional voice)
Loading state (processing)
Chat interface (answers, follow-ups, quick actions)
UI/UX only — no backend, LLM, or API work.
SCOPE OF WORK (UI/UX ONLY)
Heuristic audit and direction: identify hierarchy, spacing, contrast, and usability issues; propose quick wins and priorities.
Visual language: refine type scale, color (light/dark), spacing, elevation, and state styles to feel modern, calm, and expert.
Screen polish:
• Landing: input prominence, helper text, voice affordance, CTA hierarchy, brand lockup, responsive behavior.
• Loading: progress treatment (skeletons vs spinners), clear latency messaging.
• Chat: message layout, readable line length, timestamps, actions (copy / ask similar), empty/error/no-result states.
Microcopy: clear, compliant, human tone (no medical claims).
Interaction and motion: tasteful transitions for send/receive, loading, toasts; respect reduced-motion settings.
Design system in Figma: buttons, inputs, cards, chips, tabs, toasts, icons; variants and usage notes; tokenization for Tailwind/CSS variables.
Accessibility: AA contrast, focus states, keyboard navigation, screen-reader labels.
DELIVERABLES
Short UI/UX audit with prioritized recommendations.
Hi-fi mockups and a clickable Figma prototype for the three screens (light and dark).
Component library with states/variants and a token sheet (color, type, spacing, radii, shadows, motion).
Motion specs (Figma animations or short GIF/Lottie references).
Microcopy guide for system messages, loading, errors, and disclaimers.
Dev handoff: organized Figma, annotations/redlines, and a brief Loom walkthrough.
OUT OF SCOPE
Backend services, data/LLM configuration, authentication, analytics, or any server/API work.
WHAT WE WILL PROVIDE
Current screens and flows (landing, loading, chat) and product content.
Brand constraints (tone: calm, knowledgeable, trustworthy), logo, initial palette.
Design/engineering point of contact for quick feedback cycles.
Frontend context: Next.js + Tailwind via bolt.new (for token parity in Figma).
MUST-HAVES
Portfolio of shipped web apps (ideally chat/knowledge tools) showing polish and systems thinking.
Expert Figma skills (autolayout, variants, component properties, prototyping).
Strong interaction/motion sensibility and accessibility fundamentals.
Comfortable designing for Tailwind/design-token workflows.
NICE-TO-HAVES
Experience in regulated or retail environments; familiarity with cannabis retail workflows.
Light front-end literacy, iconography/illustration, Lottie/After Effects.
ENGAGEMENT
Timeline: 1-2 weeks
Budget: $700
Collaboration: async first; weekly design reviews; quick Looms for iteration.
HOW TO APPLY
Start your proposal with "professor" and include:
2–3 relevant web-app case studies (before→after preferred).
A one-paragraph week-one plan for our three screens.
A link/GIF to a micro-interaction you designed that improved clarity.
SUCCESS LOOKS LIKE
Cleaner hierarchy and faster comprehension on all three screens.
Chat feels confident and helpful with clear actions and friendly system states.
Cohesive visual/interaction language (light and dark) and a maintainable component library.
Smooth dev handoff with minimal ambiguity.
Apply Now
Apply Now