Bloomy! is a mobile app concept that helps users quickly find bouquet options that match their budget and schedule.

This’s an UX course project, which came from my real observations and my own experience buying flowers.

Bloomy! 是一款協助忙碌的現代人快速找到符合預算與時間的花束訂購 App 概念設計。靈感來自真實購花經驗：消費者不知道當季合理價格、或臨時需要花束卻不清楚哪間花店有空檔；而花店則常面對不如預期的預算的客人與大量來回溝通的成本。
目標：讓使用者用最少步驟找到合適花店，同時減少花店與客人之間的資訊落差與溝通成本。
工具：Figma｜時程：約 4 週｜職責：獨立 UX/UI 設計師，負責端到端設計流程
涵蓋內容：使用者訪談・問題定義・資訊架構・低保真至高保真原型・可用性測試・設計迭代

Project Overview

Problems
From the client side: Customers lack knowledge about pricing, timing, and florist availability.
From the florist side: Shops struggle with unrealistic budgets, costly back-and-forth communication and holiday capacity.

---

---

User Research

Summary

Interviews and a survey showed that infrequent and first-time buyers were overwhelmed by too many early choices. Instead of deep customisation upfront, they preferred a guided, low-effort starting point.
I therefore simplified the entry experience into three intents: ‘delivery date’, ‘budget’, or ‘browse’, to reduce decision friction and help users progress faster.

---

Paint points

---

Persona

Problem statement:

Quinn is a busy professional who needs a way to quickly find and order the right bouquet because she doesn’t have time to compare local florists or check if pickup times fit her schedule.

User Journey Map

Persona: Quinn, a busy professional with limited time. Prefers in-store collection to avoid waiting for delivery.
Goals: Find a nearby florist that fits her budget and schedule, and confirm a collection time before her partner’s birthday.

Action	Browse Shops	Choose Bouquet	Pick a Date	Select Time Slot	Confirm & Pay
Task list	Opens app, filters by budget, checks shop page	Reviews price, size and style	Taps “Select Collection Time”	Picks a slot that fits schedule	Reviews order and pays
Feeling	Wants quick, suitable options	Hopes to decide quickly	Wants immediate clarity	Needs certainty it’ll be ready	Wants a smooth finish
Opportunities	Highlight “Earliest Collection Time” and “Click & Collect”	Clearer product info and preparation time	Show available/unavailable slots upfront	Display estimated preparation time and recommended slots	Provide a concise, reassuring summary

Digital Wireframes

1. First Low-fidelity Prototype

---

• The homepage included options such as ‘By Colours’, ‘By Types’, ‘Bespoke Bouquet’, and ‘Our signature’.
• The early design focused on offering various choices, but it didn’t create any real value. It looked like a typical flower-ordering app and didn’t address any specific problem.

2. Turning Point

By observing social media (both florists and customers) and talking to my floral class teacher (who also runs a flower shop), I realised that more features do not necessarily solve users’ problems.

Interviews revealed the real pain points:

• Users don’t know the current price of flowers
• They don’t know which shop to start with, they can only rely on recommendations from friends
• They’re unsure how far in advance 
  They would like to know if they can pick up flowers today, and how long it takes to prepare a bouquet.

3. Second Version High-fidelity Prototype

• Choose time, budget, and browse randomly. The design also displays available flower shops (start from 5km radius)
• Each feature addresses a specific problem:
  Choose time solves the needs of customers with last-minute orders or those who suddenly want a bouquet
  Choose budget: bridges the information gap between customers and florists
  Browse randomly: helps potential customers who want to buy flowers but don’t know where to start

---

Usability Testing

Findings

#	Finding	Severity
1	The budget/date fields appeared interactive, prompting users to attempt typing directly into them	High
2	Action icons were too small, making them difficult to tap accurately	High
3	The peek effect on bouquet images successfully encouraged users to scroll	working as intended

Note: 3. The peek effect on bouquet images was an intentional design decision: the partially visible cards were designed to signal scrollability, confirmed by user behaviour.

Iteration

---

---

Style Guide

Going forward

Bloomy! is a mid- to high-fidelity prototype created for a UX course. Following a moderated usability test with three participants, several key insights and opportunities for improvement were identified.

Learnings & Findings

• Interviews highlighted that not everyone wants a fully automated process. Some people still appreciate 1:1 conversations with florists. The design should therefore support both quick ordering and more personalised interaction.
• The app is not simply about finding “cheap” flowers. It is about setting realistic expectations for both sides and helping people understand what is feasible within their budget and timeframe.
• Even with a small sample, early research can reveal surprising patterns. For example, how budgets relate to the emotional significance of the occasion, rather than income level alone.
• TWD 500 seems to be an acceptable starting price point: regardless of budget range, most potential customers were comfortable with this amount.

Reflection

• During the usability test, I learnt that giving participants clear, specific tasks is essential. Without guidance, users may explore the interface in unexpected ways, or confused, which can affect the reliability of the findings.

• I also discovered that users who searched by date still expected to be able to refine their results by budget, and vice versa. This suggests that the two filters should work together rather than as separate paths, and that future iterations should allow users to combine both criteria when browsing available florists.

• Finally, I had not initially considered using tag-style labels to display the selected filters. This was because I assumed the empty field would help users recall which path they had taken. But in reality, users do not need that information. What they do need is a clear visual distinction between what is selected and what is not, which the tag style communicates far more effectively.

Next steps

If I had more time and resources, I would like to:

• Conduct a second round of usability testing with a larger and more diverse group of participants, including florists, to validate the revised designs.
• Expand the florist-facing features: enabling shops to upload signature bouquets, manage their calendars, and define how far in advance customers can book (for example, up to three months).
• Explore ways to better support special requests, such as table arrangements for events, not only bouquets.

Thanks for reading.
Hope you enjoyed the journey.