Lazy Bartender
A cocktail recipe application allowing users to make the most with what they have on hand.
Currently In development, launching February 2025
Project type: Mobile Application
Industry: Food and Beverage
Role: Research, UX/UI, Branding, Prototyping and Testing
Our Story
One afternoon, Alex noticed his liquor cabinet full of half-empty bottles and decided to make a drink. Overwhelmed by the mental juggling of cocktail options, he defaulted to his go-to Old Fashioned, leaving the lesser known ingredients untouched.
As a Software Engineer, Alex set out to optimize his collection and discover new drinks in the process. After drafting a version that only engineers could love he brought me on to design a product that was not only effective, but a joy to use. Along with the UX/UI design I developed a monetization strategy and outlined a roadmap for future feature releases.
Question
We all have them: the Fernet your Hipster friend gave you for Christmas, the Coconut Rum for a pina colada last summer, and a Gold Schnapps that you impulse bought “because there’s no way that it’s real gold right?”
Target User
Adults age 25 to 40 with a moderate collection of liquors and novice understanding of cocktail making.
Insight to HMWs
Challenge
Why would someone use an App when they can use google or another search engine?
“Hey Siri, what can I make with this Creme de Cocoa? Also, what is Creme de Cocoa?”
How might someone maximize the random liquors and liqueurs collected over the years?
Our Answer
Make it personal! Only display the cocktails relevant to the user based on what they have on hand. This provides a framework to discover without being overwhelmed by endless choices.
UX
After analyzing various aspects of our competition, including task flows, aesthetic character, and business models, we organized the app's goals and divided them into UX and UI categories.
What we don’t
“Premium Membership Content” strategy. We do not want to be responsible for collecting and processing user payment information for security reasons
White backgrounds feel wrong since a cocktail app will primarily be used at night
Too many features and options making it possible to endlessly scroll through app
Cartoon images do not fit the desired audience
Lots of text bubbles that make app feel “input/ output”
Too many colors create the lack of aesthetic consistency
UI
First, thinking of our target audience, we wanted the UI to be viewed as “Refined and Direct with just a hint of Whimsy”.
Clean aesthetic with a simple color palette.
Real images of Drinks (because we eat with our eyes)
Soft dark background as the app would be used primarily at night
Limited text bubbles
Reminiscent of cocktail menu at a restaurant
Serif Font for Headers. Sans Serif for button and body Text
Competitive Analysis
Before starting the design process, we analyzed various recipe-based apps to identify features and UI that contribute to their success/ failure. Below are three apps that take somewhat different approaches to achieving the same goal: finding a recipe.
At first, we joked that the product should be so simple it could be used while drunk. This joke soon became our mantra and shaped the design of the users experience.
Minimize steps taken to arrive at recipe
Prioritize curated list of recipes available based on the users input
Recipe breakdown to be short and concise
Intuitive method of adding ingredient to list
Multiple interaction points to add ingredients to list as users may forget or fail to enter all ingredients on first attempt
Indicate additional drinks may be possible with few extra ingredients
What we like
Ability to search ingredients and drink recipes
Real Images of the cocktails
Ability to sort and search by flavor profiles, strength, difficulty to make
Clear indication of ingredients and number on hand for recipe
Ability to save recipes for later
Themed categories that provide a playful component to app
Design Guideline
Information Architecture
By breaking out the percentage of time spent on each task, we established a design framework to guide us. For instance, we aim for users to spend only 10% of their time adding ingredients to their bar. Therefore, this process needs to be simple, intuitive, and quick
App usage Breakdown
Designing with, not for Developer
The engineer selected React Native for the project, and I adapted my designs to its constraints to optimize the user experience. Collaborating closely, we reviewed scripts and JSON files together, streamlining development and ensuring alignment.
In my years working with various designers and contractors, I learned that understanding how a product is made enhances communication and leads to better outcomes.
Mockups and User Testing
After creating the following mid-fidelity mockups, we gathered four volunteers and provided the brief: Use the app to input ingredients and find a recipe. We observed their interactions with the product, answered any questions, and asked for their initial opinions.
What Worked
Finding and adding ingredients was easy
Users intuitively navigated from page to page
Layout of the Recipe page was clear and direct
Search command was appreciated by user who didn’t want to spend time scrolling through ingredients
Priority Fixes
What Didn’t
One volunteer described a lack of clarity on what the first step to achieving the goal was. Should they go straight to the recipe tab or required to enter ingredients to proceed? “I’m not exactly sure what to do first”
Interface lacked a clear way of seeing all the ingredients selected without scrolling through the entire list
No need to have separate tabs for “Favorite” and “Saved” Drinks
The most important fix was to clearly define a path to the users end goal: finding a drink recipe. It was determined that the cause of this confusion lay in the visual ambiguity of the Navigation Bar. With every Tab in a flat line, sharing the same size and color, the navigation lacked programatic hierarchy.
Previous Navigation
Revised Navigation
The Previous Navigation was flat, with all tabs holding the same visual and perceived value. This lead to ambiguity about the main goal of the product.
The Revised Navigation distinguishes the Drinks tab highlighting it as the resolution page for the product.
Secondary Fixes
Add landing page to prompt the user on how to begin and provide opportunity for discovery
Add a separate page to clearly list all ingredients selected with ability to add ingredients via search
Remove “Saved Drinks” page as it seems superfluous
Style Guide
Revenue Source
We decided early on that the Lazy Bartender would avoid subscriptions, data collection, and premium charges. This approach not only eliminates security risks but also aligns with the alcohol industry's massive advertising budgets—Anheuser-Busch alone spent over $591 million on ads in 2017*.
Instead of intrusive pop-ups, we opted for seamlessly integrated ads. For instance, if Jack Daniels were a sponsor, the “Old Fashioned” recipe could subtly feature their branding, enhancing the user experience without disruption.
If a company sponsors 10 recipes for a year at $100 a recipe that would entail $1000 dollars a year in revenue. With over 700 recipes in our current library this provides ample opportunities for sponsorship.
* Source: Advertising Age-Neustar. 200 Leading national advertisers 2018 fact pack. 2018, via the National Library of Medicine
What’s Next?
Additional User Testing
How does the product work on its fifth and tenth open?
Will adding new ingredients add enough drinks to keep users interested?
Will the introduction of advertisements turn users off from the app?