Introduction
I came up with Fiori Fuori when I was studying Italian and thought it had a nice ring to it; "fiori" means flowers and "fuori" means outside. Go outside, touch grass (flowers)! In concept it's a fun little companion app for both aficionados and clueless chaps (me) alike to learn about flowers, biology, and culture, helping us all be more inspired shoppers.
Discovery
My background research included a competitive audit (Instacart, boutique online flower shops, etc.), reading blogs on common design challenges in the space, and interviewing people of varying backgrounds and levels of experience with flowers. Based on what I gathered, I created two user personas, defining key pain points.
Prototyping & Testing
I created a Figma prototype for my "flower shopping app" and tested it in a remote moderated usability study. I provided prompts for completion in app, took note of their behaviors and reactions, and asked follow-up questions. The insights I gathered from this study unearthed the true value of what this app could be, and I made it bloom in the following iterations.
Reflection
This project illustrates the importance of treating each iteration of a product like a hypothesis. When tough feedback came in, I had to be willing and able to make significant changes to my design. Great insights emerged from the scientific process, but of course it was still up to my intuition & creativity to come up with better solutions. Adaptability paid off; testing with the current version showed that users were significantly more satisfied by the end of their journey and twice as likely to purchase flowers.
Standing on Business
Sometimes a UX problem can be an indicator of how the business model needs to adapt. For example users' uncertainty about flower delivery as an option might not be best fit to solve purely through UX, and thus not worth the investment if greater value can be created by modifying the business itself. However, just because UX might not be the solution doesn't mean the design process is not worthwhile. The insights revealed can save a company from going down an expensive path with low returns; in this case sidestepping the complex and costly endeavor of integrating delivery services.
What's Next?
A library of robust, bucketed information on every flower type imaginable. More popular and common flowers could receive higher-fidelity cards with detailed, dynamic, and manually curated content, with a more boilerplate card structure to fall back on for lesser-known varieties. Like how Spotify embellishes the music player interface with special features such as lyrics, videos, tour info, merch links, etc. for popular songs and artists.
Shop— screens for viewing details of a flower shop & browsing their flower selections. Feature ideas: sort methods i.e. relevance, price.
A simplified "orders" screen that is redesigned for in-app orders being exclusively pickup. Feature ideas: satisfaction guarantee and/or time-sensitive order canceling.
App for business side, likely large screen based, for flower shops to list their store on the map, add flowers they have in stock, and other necessary operating tasks. The service would need to offer an enticing compensation model for partner shops due to likely incurring added costs.
