After creating my solution directions from my research, I decided to do an idea brainstorming session where I wrote down several key features and individual micro-features or ideas that could accompany them. The idea was to write a variety of ideas, with no restriction on cost, code, or existing market features.
I decided to combine several of the new ideas into a singular feature that I had initially wanted to design after user research - a custom bouquet feature. Many of the ideas above, such as more detailed information for each flowers or 3D / augmented reality depictions can be utilized in this feature.
Because custom bouquet features generally have a very similar linear flow, instead of testing design alternatives I decided to begin designing for an improved version of existing custom bouquet features.
Iteration one revolves mainly around having sizes in the bouquet. It allows the users to pick between four sizes, each with a set number of flowers/stems the user can pick. The initial aim was to simplify the users' process, attempting to reduce choice paralysis on the flower selection screen by limiting the number of flowers they can pick. The full user flow involves four screens.
I presented this feature alongside the entire Bloomer app to close friends and peers at UCI to gather some insights. Since I had already designed some basic wireframes on Figma, I let the participants interact with them, asking them to perform moderated tasks, such as creating a custom bouquet of five flowers.
Users enjoyed the flow as an idea; however, there were some limiting features that muddled their experiences.
This iteration of design improves upon the first iteration in several ways due to the usability testing.
- Stepper / Progress Tracker: I decided to add a stepper at the top of the feature, showing the user where they are in the custom bouquet creation process, as many users complained about confusion in terms of length of the process. This also doubles as navigation, as users can press one of the three page names to go back and forth.
- View Selection Button: Users can click this button to quickly view at their full bouquet selection and make changes easily
- Search Functionality: Added a search button for users to quickly parse through
- Increased visibility of CTA Button: Added a sticky button at the bottom of the page, showing users at all times the next step
Most users reported back with a more positive experience with this iteration, claiming it was "more clear what [they] had to do [during the entire process.]" Improvements through added features like a sticky button and restructured UI proved to raise their experiences. However, with these new features, some were not implemented in the most ideal way, leading to confusion and mixed emotions as depicted below.
After going through rounds of usability testing, I decided to both incorporate old, positively-received features and and add new additions, as described below in the graphic.
A large issue for confusion I found while testing was uncertainty on navigation. Previous iterations utilized singular CTA buttons at the bottom of the page moving the user to the next step of customization; however, many users voiced confusion about the linear path through customization and "if the back button exits the entire feature or just the current page" or how to go back to edit their bouquet due to a change of mind. I decided to employ more of a split navigation style versus the previous very linear navigation style to help this issue.
Additionally, aside from the new navigation style, I utilized changes in certain buttons, such as the visual rework of the "View Selection" button, to make the screen less visually cramped and refined other details as well, as shown below!