Lotusque Website
Case Study · Responsive Web Design · UX/UI

Lotusque
Responsive Website

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

Duration
Sep – November 2022
3 months
My 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 seamlessly 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 here 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
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
Facilitate the online ordering process for users while providing florists with an organised, easy-to-manage system for receiving orders.
📐
Responsive First
Designed to work flawlessly across desktop, tablet, and mobile — with layouts adapted specifically for each breakpoint.
02 — User Research

Same users, new context

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

01
Limited shop access
Buyers often need flowers at times 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 were missing from competitors.
03
Time pressure
Web users expect faster checkout than in-store. Every extra click or confusing step is a reason to abandon the order entirely.
04
Freshness uncertainty
Without seeing flowers in person, users needed trust signals — stock availability, freshness guarantees, and delivery timing.
03 — Personas

Who we're designing for

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

Persona Lily

Lily — fashion designer needing access to exotic, fresh flowers for her projects

Persona Mark

Mark — busy entrepreneur who needs to order bouquets online without visiting a shop

04 — User Journey Maps

Mapping the web experience

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

Journey Map 1

Lily's journey — finding and ordering exotic flowers for a creative project

Journey Map 2

Mark's journey — ordering a bouquet quickly between meetings

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

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.

Digital Wireframe 1

Desktop wireframe — homepage layout and navigation structure

Digital Wireframe 2

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.

Lo-Fi Prototype

Lo-fidelity prototype built in Adobe XD — used for round 1 usability testing

06 — Usability Studies

Testing revealed two critical fixes

I conducted two rounds of usability studies before finalising the design. Participants consistently flagged two major issues — both of which were directly addressed in the next iteration.

Fix 1 — Navigation overhaul

Before usability study
Before
The top menu had two rows, which caused confusion for users. Elements were also too large, making it feel crowded and hard to scan.
After usability study
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 usability study
Before
There was no space for users to provide special instructions to the florist — a feature participants specifically asked for during testing.
After usability study
After
Added a dedicated instructions section in the checkout flow — allowing users to communicate specific requirements directly 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 consistent visual language.

Mockup 1

Desktop homepage — product discovery and hero

Mockup 2

Desktop product catalogue — category browsing

Mockup 3

Bouquet detail and customisation view

Mockup 4

Checkout flow with florist instructions field

Mobile Screens

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

Mobile 1
Mobile 2
Mobile 3
Mobile 4

High-Fidelity Prototype

Hi-Fi Prototype

Final high-fidelity prototype — complete responsive flow in Adobe XD

Explore the 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 key principles guided every decision.

01
Alternative text
Provided descriptive alt text for all images — essential for users who rely on screen readers to understand page content.
02
Plain language
Written in clear, simple language throughout — no jargon, no technical terms, no complex sentence structures that might exclude users.
03
High contrast
Ensured 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
The two usability study fixes — streamlining the nav and adding the instructions field — were both direct results of watching real users struggle. Testing is non-negotiable.
Next steps
Explore a tablet-optimised layout, add a florist-facing order management dashboard, and conduct accessibility audits with assistive technology users.