UX / UI Case Study

Lotusque responsive website

Extending the Lotusque bouquet ordering experience to the web, designed responsively across desktop, tablet, and mobile.

RoleUX/UI Designer ScopeResearch, Wireframes, Prototype, Usability testing TypeResponsive website
Duration
September to November 2022
3 months
Role
UX Researcher, UI Designer
Tools
Adobe XD
Wireframing, Prototyping
Platform
Responsive Web
Desktop, Tablet, Mobile
01 · Overview

From app to web

Following the success of the Lotusque mobile app, this project extended the bouquet ordering experience to a fully responsive website, ensuring users could order flowers from any device, whether at their desk or on the go.

"Despite my initial belief that most users preferred buying flowers in person, the majority indicated a preference for purchasing online."

The challenge wasn't just replicating the app; it was rethinking the experience for a wider canvas, while keeping the same simplicity and ease that made the app successful.

🌐
The problem
Cluttered, non-responsive competitors

In a fast-paced world, people want to buy flowers online without friction. But existing websites were cluttered, confusing, and not optimised for all screen sizes.

The goal
Effortless online ordering

Make online ordering easy for users, while giving florists an organised, easy-to-manage system for receiving orders.

📐
Responsive first
Built for every screen

Designed to work across desktop, tablet, and mobile, with layouts adapted specifically for each breakpoint.

02 · User research

Same users, new context

The core pain points from the app research still applied, but this study focused on web-based flower purchasing behaviours, including how users navigate and discover products on desktop versus mobile.

🕗
01
Limited shop access
Buyers often need flowers when physical shops are closed. A web solution available 24/7 directly addresses this gap.
💬
02
Knowledge gaps
Users wanted better information about flowers online: descriptions, care instructions, and occasion guidance that competitors were missing.
03
Time pressure
Web users expect faster checkout than in-store. Every extra click or confusing step is a reason to abandon the order.
🌸
04
Freshness uncertainty
Without seeing flowers in person, users needed trust signals: stock availability, freshness guarantees, and delivery timing.
03 · The users

Who we're designing for

The same two personas from the app project guided this design, with added consideration for how each uses the web differently from a mobile app.

"Fresh flowers aren't just props, they're part of how I design. I just can't lose hours hunting for them."
Age25RoleFashion DesignerHomeMontreal, QCFamilyPartner & their dogEducationFine Arts, B.Sc.
Goals
  • Easily order fresh flowers for her designs and photoshoots
  • Find unique, exotic flowers her local shop doesn't carry
  • Start her own business
Frustrations
  • A busy schedule leaves no time for trips to a flower shop
  • Can't find the unusual flowers her work needs
  • Some florists lack knowledge about the flowers themselves
About

Lily is a young fashion designer who treats flowers as an essential element of beauty. She experiments with arrangements as props for her contemporary, boldly patterned designs, and loves working colour and texture into her work in unexpected ways. Fresh flowers around her home and studio keep her feeling calm and inspired, though her schedule rarely allows the shop visits her craft depends on.

"I want to surprise my family with flowers, I just don't have time to stand in a shop to do it."
Age48RoleEntrepreneurHomeNew York, NYFamilyWife & two daughtersEducationMBA
Goals
  • Spend more time with family
  • Grow his business
  • Throw a big party for their 25th wedding anniversary
Frustrations
  • Many florists still operate traditionally, with no online ordering
  • Spending time going to a physical shop is a drain
  • Not being able to order bouquets in advance complicates things
About

Mark is an ambitious entrepreneur running a young startup on a demanding schedule that often keeps him working late. Family matters deeply to him, and he loves surprising them with flowers and gifts whenever he can. His assistant used to handle ordering, but since she left for maternity leave he's been managing it himself, and struggling to find the time these tasks demand.

04 · User journey maps

Mapping the web experience

Journey maps helped identify the emotional highs and lows through the ordering process, revealing exactly where friction needed to be removed.

How to read these. The curve tracks how each user feels at every stage: above the line is delight, below is friction. Each stage is tagged by where its insight comes from: Persona-based (from the user's stated goals and frustrations), Review-informed (matching recurring themes in public reviews of comparable flower apps), or Assumption (my inference, still to be tested).
Persona 1 · Mark
Mark's journey: ordering to surprise his family

How might we let Mark order a fresh bouquet online, in advance, without carving time out of a demanding schedule?

The emotional low point is checkout, and it isn't just a hunch. Reviews of comparable flower-delivery apps repeatedly flag hidden fees and long payment flows at this exact step. Delight climbs while he customizes, then collapses at checkout. Reducing that friction is the single highest-impact opportunity in the journey.
Emotional journey
Delighted Neutral Frustrated Delight collapses here
01
Download & discover
Assumption
Feeling
Curious
Doing
  • Download the app
  • Search for flower shops
  • Pick a shop
OpportunityGuide the choice: too many shops to sift through.
02
Customize the bouquet
Review-informed
Feeling
ExcitedHesitant
Doing
  • Choose a style
  • Customize flowers & foliage
  • Add a note
OpportunityLet users add a gift: add-ons are a common ask in reviews.
03
Review the order
Review-informed
Feeling
ImpressedStressed
Doing
  • Confirm the customization
  • Check the price
  • Add to cart
OpportunityShow a true preview: "not as pictured" is the #1 complaint in reviews.
04
Place the order
Review-informed
Feeling
StressedOverwhelmed
Doing
  • Go to checkout
  • Choose a delivery time
  • Enter address
  • Pay
Key opportunityShow fees early and save address/payment: reviews flag hidden costs and long checkout here.
05
Track delivery
Review-informed
Feeling
RelievedGladExcited
Doing
  • Get confirmation
  • Track the order status
OpportunityReal-time tracking and status notifications: late or unclear delivery is a top complaint.
Positive emotion Friction Highest-impact opportunity
How I built this. Emotions and pain points were shaped by analysis of public reviews of comparable flower-delivery services (Trustpilot, BBB, and consumer review roundups), which repeatedly surfaced friction around hidden checkout fees, long payment flows, "not as pictured" arrangements, and unclear delivery tracking. Stages marked Review-informed map directly to those recurring themes; the discovery stage is marked Assumption where direct evidence was thinner. Next step: validate with 3 to 5 moderated usability tests.
Persona: Mark, the busy entrepreneur ordering bouquets to surprise his family · Scenario: order online, in advance, without visiting a shop
Persona 2 · Lily
Lily's journey: sourcing flowers for her work

How might we help a designer source fresh, unusual flowers, and trust they'll arrive in time for the shoot, without losing hours to shops?

Lily's stress peaks earlier than a typical shopper's, at freshness and timing, not payment. Because she depends on flowers for professional work, the risk isn't a clunky checkout; it's ordering exotic stems and not trusting they'll arrive fresh and on time for a shoot. That's where the experience has to earn her confidence.
Emotional journey
Delighted Neutral Frustrated Freshness & timing stress
01
Discover & search
Persona-based
Feeling
HopefulSkeptical
Doing
  • Open the app
  • Search for exotic & fresh flowers
  • Filter by type, color, rarity
OpportunityStrong filters for type, color and rarity: she can't find exotic stems locally.
02
Browse & learn
Persona-based
Feeling
ExcitedInspired
Doing
  • Explore what's exotic & in season
  • Read flower details & care info
  • Save favorites
OpportunityRich flower info (origin, care, vase life), since many florists lack this knowledge.
03
Customize & preview
Review-informed
Feeling
CreativeHesitant
Doing
  • Build a custom arrangement
  • Preview the result
  • Set quantity for a shoot
OpportunityAn accurate preview: "not as pictured" is the top complaint in flower reviews.
04
Order & schedule
Review-informed
Feeling
AnxiousStressed
Doing
  • Confirm freshness & stock
  • Schedule for the shoot date
  • Choose delivery or pickup
  • Pay
Key opportunityGuaranteed freshness, firm delivery windows and fees shown early: a missed date can wreck a shoot.
05
Receive & create
Review-informed
Feeling
RelievedDelighted
Doing
  • Receive the flowers
  • Check the quality
  • Use them in her designs
OpportunityQuality guarantee and easy fix if stems arrive wrong: reliability she can build on.
Positive emotion Friction Highest-impact opportunity Persona-based Review-informed
How I built this. Lily had no prior journey, so I mapped it from her stated goals and frustrations (Persona-based) and cross-checked it against recurring themes in public reviews of comparable flower services: "not as pictured" arrangements, hidden checkout fees, and unreliable delivery (Review-informed). Because Lily depends on flowers professionally, her stress peaks not at checkout but where freshness and shoot-date timing are on the line, a deliberate contrast with Mark's journey. Next step: validate with 3 to 5 interviews with designers who source flowers for their work.
Persona: Lily, the fashion designer sourcing fresh & exotic flowers for her designs · Scenario: find unusual stems and get them in time for a shoot
05 · Design process

Building the web experience

01
Paper wireframes
Sketch layouts fast
02
Digital wireframes
Structure in Adobe XD
03
Lo-fi prototype
Test before visual design
04
Usability studies
2 rounds of testing
05
Hi-fi prototype
Final responsive design
Paper wireframes

Paper sketches let me explore multiple layout directions quickly, particularly around the navigation structure and homepage hierarchy, which differ significantly between desktop and mobile.

Paper wireframes for the website
Hand-drawn paper wireframes exploring desktop and mobile layout options
Digital wireframes

Moving into Adobe XD, I developed digital wireframes focusing on information hierarchy, navigation patterns, and the responsive grid across breakpoints.

Desktop wireframe
Desktop wireframe: homepage layout and navigation structure
Product browsing wireframe
Product browsing and category filtering wireframes
Low-fidelity prototype

The lo-fi prototype was used in the first round of usability testing to validate the information architecture and core user flows before any visual design was applied.

Low-fidelity prototype in Adobe XD
Lo-fidelity prototype built in Adobe XD, used for round 1 usability testing
06 · Usability studies

Testing revealed two critical fixes

I ran two rounds of usability studies before finalising the design. Participants consistently flagged two major issues, both addressed in the next iteration.

Fix 1: Navigation overhaul
Before
Navigation before
The top menu had two rows, which confused users. Elements were also too large, making it feel crowded and hard to scan.
After
Navigation after
Revised to a single clean row. All elements were scaled down and simplified, making scanning and navigation significantly faster.
Fix 2: Florist instructions field
Before
Checkout before
There was no space for users to provide special instructions to the florist, a feature participants specifically asked for during testing.
After
Checkout after
Added a dedicated instructions section in the checkout flow, letting users communicate specific requirements to the florist before payment.
07 · Final mockups

Refined across every screen

After both rounds of usability testing, the final high-fidelity designs were produced, polished across desktop and mobile with a consistent visual language.

Desktop homepage
Desktop homepage: product discovery and hero
Desktop catalogue
Desktop product catalogue: category browsing
Bouquet detail
Bouquet detail and customisation view
Checkout
Checkout flow with florist instructions field
Mobile screens

The design adapts fully for mobile, with condensed navigation, thumb-friendly touch targets, and simplified layouts that prioritise the core ordering flow.

Mobile screen 1
Mobile screen 2
Mobile screen 3
Mobile screen 4
High-fidelity prototype
High-fidelity responsive prototype
Final high-fidelity prototype: complete responsive flow in Adobe XD
Explore the prototype

Try the interactive prototype

Click through the full interactive responsive prototype in Adobe XD.

Open in Adobe XD ↗
08 · Accessibility

Designing for everyone

Accessibility was built into the design from the start, not added as an afterthought. Three principles guided every decision.

🔤
Alternative text

Descriptive alt text on all images, essential for users who rely on screen readers to understand page content.

✍️
Plain language

Clear, simple language throughout: no jargon, no technical terms, no complex sentence structures that might exclude users.

🌗
High contrast

Sufficient contrast between text and background colours, critical for users who are colourblind or have low vision.

09 · Reflection

What I learned

Translating a mobile app to a responsive web experience taught me that responsive design is not just scaling up; it's fundamentally rethinking how users interact with content at different screen sizes and contexts.

💡
Key insight

Desktop users browse differently from mobile users. Navigation patterns, content density, and interaction models need to be reconsidered for each breakpoint, not just resized.

🔧
Design lesson

Both usability fixes, streamlining the nav and adding the instructions field, came directly from watching real users struggle. Testing is non-negotiable.

🚀
Next steps

Explore a tablet-optimised layout, add a florist-facing order management dashboard, and run accessibility audits with assistive-technology users.

Lotusque Website · UX/UI case study: overview, research, personas, journey maps, process, usability, final mockups, accessibility, and reflection.