Phase three

Information architecture

After everything is kinda sorted out, the next step is to create

information architecture. Organizing and labeling the content to be easily understood by users, and ensuring its usability, findability, flexibility, and consistency.

Categories

Special offers

Shopping cart

Payment options

Broker

Broker

Main screen

Browse menu

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Still waiting

Preparing

Coming to you

Beverages

Desserts

Filters

Coffees

Order status

Pay offline

Scan the code

Apple Pay

Call the waiter

Google Pay

Pay with card

NFC-enabled device

Enter loyalty card no.

Optional

Pay online

Call the waiter

Optional

User flow

The last piece of the puzzle.

User flow is the precursor to the next and final stage of this task -creating a user interface for this app.

Phase two

This section is all about assumptions, constraints, and eventual trade-offs that were made.

Assumptions:

  1. We can assume that users actually have seen the front-door kiosk display with free-spots-available counter
  2. Users have basic knowledge of how to order from a digital menu
  3. Users have Google Pay, Apple Pay, or NFC-enabled device
  4. Users could pay with cash
  5. Old-aged users don't have mobile phones with the ability to scan QR codes, or don't have phones at all
  6. Users know English. This app could be multilingual (Serbian/English)
  7. Users won some giveaways from social media and now they have discount code/loyalty points
  8. Users want to have user accounts
  9. Cashier service is fast and reliable
  10. The reviewing system is gonna be used a lot

Constraints:

  1. Users can have account profiles, but only created from another device
  2. Only The Cafe tablets should have this app installed
  3. There are three options for payment OnlineCashier serviceCall the waiter/waitress
  4. Invoices can be sent by e-mail with, or without a previously created user profile
  5. Discounts and loyalty points could be given with some kind of loyalty card with its unique number associated with the user. In this case, The Caffe encourage users to have that kind of card and make user profiles and be our loyal everyday consumers

Trade-offs:

  1. Users can create a user account. Users’ top priority is to have a piece of mind time while drinking their coffee or enjoying their dessert. Therefore, there shouldn’t be any barrier to using the app. Without having to create an account, users can interact with the app.Assuming that users, especially tourists can come to The Cafe only once, there’s no strong need for creating a user profile.
  2. Even though I wanted this whole experience to be a fully-digital app with no need for a waiter in terms of paying the bills, a scenario with the old users and those users who aren't tech-savvy was quite possible so I created one more option called Call the waiter.

A smarter way to order at the café

Designed for comfort, built for speed.

ABOUT THE PROJECT

The Café App is a tablet-based ordering system that lets customers browse menus, find free tables, and pay, without waiting

for staff.

 

I led the full product design—from research and user flows to branding and UI, crafting a seamless in-store experience that blends modern tech with real-world hospitality.

Role

UX/UI Designer

Scope of work

Competitive analysis

Information Architecture

User flows

Prototyping

Logo/branding

Client

the Cafe

Type

iPad app

Timeline

2 weeks

Final phase

UI design

I’ve immediately jumped onto high-fidelity designs, so, the Lo-fi prototype and wireframes are missed here. After all, some of the constraints when building a new app or system, are actually wireframes. Fast-moving environments need fast solutions and rapid prototyping and quick Candy-like UI is one of them.

The Logo

I’ve made a quicky-simple, and yet (in my opinion) a quite remarkable logo for this coffee shop. I’ve opted for the main color to be yellow, because of its joyful characteristics.

The main screen

Using yellow as the main color and black as the contrast color, the main screen follows the logo style. I wanted everyone who’d sit for the first time in The Caffe to feel the same “offline” vibe when opening the printed menu.Also, I’ve chosen the portrait mode of the tablet, just because (once again) everyone to feel more natural when will “flipping pages” of this digital and modern menu.

Home screen

When the user clicks on the Browse menu, immediately is opened the home page. Here users can find all the products, as well as current special offers.

Categories are placed on the left side of the screen, simply because this menu doesn’t mean to be one-more-mobile-product-Dribbble-app.

Products

The price of the products is mandatory for these kinds of apps, so users can see

that info first. Reviews from other users are presented as stars, and the estimated time for that particular product to come to your table is also presented in the Product Cards. Additionally, the number of calories (if there’s info for it) could be presented there.

Detailed product description

On this screen, users can learn everything about the product. From reviews from the customers, the type of the product (vegetarian, vegan, etc.) to the real story about that product. Ingredients easily could be added and removed, and a really nice addition is the info about the dietary or allergic products. The next step from here is Add to cart, where users can pay for the product, or can continue to browse for more desserts, beverages, and coffee, so they can order later on.

Check out

This screen is known to everyone I guess, as we living in the “Ordering” society. Info about the estimated time of the arrival of the all products is something we don’t see much on ordering pages, so it’s a big plus for customers who are enjoying The Caffe for the first time.Loyalty card feature is presented there as well, whether there are points for some product or discount.

Payment options

So, the final step of the user journey is, of course, payment. Scanning the code, or calling the waiter - offline methods or online methods via Google Pay, Apple Pay, or Card are options that are opted for the users.

One last takeaway

Desing assumptions always will be only assumptions. What’s actually matter is real data, real research and real testing. If our assumptions we’ve felt on our skin, then we’ve achieved so much.

 

Not every digital user is knoweledable about everythig, and not every smart user is the best digital user.

Keep in mind on it!

Design process

Goals & Tasks

So, when I find out what the brief is, the next step was to anticipate actual goals and micro-tasks for the users.

User goals:

  1. Learn about free tables
  2. Order immediately
  3. Pay

User tasks:

  1. Search through categories (if there are any)
  2. Filter by price/review/etc. for coffee/deserts/beverages
  3. Pick and order
  4. Choose how to pay
  5. Sent the invoice to the e-mail

Phase one

In this section, I’ve deep-dived into understanding the users by forming and articulating user journeys, user flow, and understanding their priorities

and pain points. Personas would be a good addition here, but, since I’ve put all my assumptions about priorities and pain points, I realized that Personas wouldn’t be in so much

great favor here.

User priorities:

  1. Find a suitable table
  2. Find a properly brewed coffee
  3. Learn how the coffee is made
  4. Ingredients of the coffee (ratio/percentages/calories...)
  5. Pay with card
  6. Pay with cash
  7. Send invoices by e-mail for better management of their expanses
  8. Make user profile for quick choices (fave coffee/desert, Invoices, loyalty points/discounts)
  9. Use discounts

User pain points:

  1. Trying to find a suitable coffee or desert
  2. Navigating the ordering apps could be a long and painful process
  3. Not sure what ingredients are used
  4. Not being able to find allergic or non-dietary products
  5. Waiting for a long time in line to make the payment
  6. Not seeing a waiter or waitress to wave a hand for making a payment
  7. Not being able to scan the QR code to make an “offline” payment

User stories

User stories helped me to understand context, motivation, and desired outcomes.

  1. Walking through Knez Mihailova user’s attention is getting caught by a huge “kiosk” display with the saying “Welcome to The Cafe where technology meets our present”. Here actually are displayed free spots/free tables which are the main goal for users to step in
  2. Finding the perfect spot
  3. Searching for the best coffee in the town
  4. Want to find all the ingredients in the coffee or desert
  5. Wanna pay immediately
  6. Invoices want always to be sent via e-mail
  7. Want to make a user profile
  8. Faved coffee wanna be ordered quick with one click
  9. Want to pay fast with stored card

User journey

What steps do users take when interacting with the app.

Before, during, and after!

  1. Walks down the street
  2. Seeing big display
  3. Steps in the shop
  4. Finds free table
  5. Scanning really fast the whole app
  6. Finds the categories
  7. Filtering by price/availability/reviews
  8. Looking for the calories
  9. Ordering the coffee/desert
  10. Question about payment
  11. Question if there are any loyalty points or discounts
  12. Choosing payment with Google Pay/Apple Pay or maybe NFC pay
  13. Choosing offline payment (cashier method) *
  14. Choosing call the waiter method *
  15. Choosing invoice to be sent to user’s e-mail address
  16. Clicks okay, returning to the main screen
  17. Picks the order
  18. Enjoying peace of mind time
  19. Continuing walking down the street

* Things should be noted here about offline payment

When users choose offline payment there will be two options

presented - Pay to cashier or Call the waiter

Pay the cashier means that the user needs to scan a QR code or just take a photo of it, then present it to the cashier and proceed with the payment.This is a good option when users don't wanna wait for the waiter or waitress to come by and give them their bill. Quite a fast process, but, there’s always a chance to wait in line for some time.

Call the waiter option is actually made for the old people, or for the users who don't have cameras on their mobile phones. Once the order is done, on the main screen of the device would be visible some kind of sticky message about the payment that needs to be done, and there will be an additional Call the waiter button, which it’s not gonna be presented if a user chose other two options. When the cashier or waiter clicks OK on their devices, that means that the bill is sorted out and the invoice will be sent to the user’s e-mail, of course, if that option is ticked in.

Loyalty card

Before we jump into the Check out and Order options, there’s one thing the user needs to answer - if he/she has a loyalty card or not.If the answer is yes, then users need to fulfill the info, and after that checkout is ready for them with all the discounts which are given as the loyalty card owner.

Mobile app

Web app

Smoodo

Craft. Track. Deliver.

Next project

Mobile app

Verve

Museums. Reimagined.

Previous project

Phase two

This section is all about assumptions, constraints, and eventual trade-offs that were made.

Assumptions:

  1. We can assume that users actually have seen the front-door kiosk display with free-spots-available counter
  2. Users have basic knowledge of how to order from a digital menu
  3. Users have Google Pay, Apple Pay, or NFC-enabled device
  4. Users could pay with cash
  5. Old-aged users don't have mobile phones with the ability to scan QR codes, or don't have phones at all
  6. Users know English. This app could be multilingual (Serbian/English)
  7. Users won some giveaways from social media and now they have discount code/loyalty points
  8. Users want to have user accounts
  9. Cashier service is fast and reliable
  10. The reviewing system is gonna be used a lot

Constraints:

  1. Users can have account profiles, but only created from another device
  2. Only The Cafe tablets should have this app installed
  3. There are three options for payment OnlineCashier serviceCall the waiter/waitress
  4. Invoices can be sent by e-mail with, or without a previously created user profile
  5. Discounts and loyalty points could be given with some kind of loyalty card with its unique number associated with the user. In this case, The Caffe encourage users to have that kind of card and make user profiles and be our loyal everyday consumers

Trade-offs:

  1. Users can create a user account. Users’ top priority is to have a piece of mind time while drinking their coffee or enjoying their dessert. Therefore, there shouldn’t be any barrier to using the app. Without having to create an account, users can interact with the app.Assuming that users, especially tourists can come to The Cafe only once, there’s no strong need for creating a user profile.
  2. Even though I wanted this whole experience to be a fully-digital app with no need for a waiter in terms of paying the bills, a scenario with the old users and those users who aren't tech-savvy was quite possible so I created one more option called Call the waiter.

A smarter way to order at the café

Designed for comfort, built for speed.

ABOUT THE PROJECT

The Café App is a tablet-based ordering system that lets customers browse menus, find free tables, and pay, without waiting

for staff.

 

I led the full product design—from research and user flows to branding and UI, crafting a seamless in-store experience that blends modern tech with real-world hospitality.

Role

UX/UI Designer

Scope of work

Competitive analysis

Information Architecture

User flows

Prototyping

Logo/branding

Client

the Cafe

Type

iPad app

Timeline

2 weeks

Phase three

Information architecture

After everything is kinda sorted out, the next step is to create information architecture. Organizing and labeling the content to be easily understood by users, and ensuring its usability, findability, flexibility, and consistency.

Categories

Special offers

Shopping cart

Payment options

Broker

Broker

Main screen

Browse menu

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Still waiting

Preparing

Coming to you

Beverages

Desserts

Filters

Coffees

Order status

Pay offline

Scan the code

Apple Pay

Call the waiter

Google Pay

Pay with card

NFC-enabled device

Enter loyalty card no.

Optional

Pay online

Call the waiter

Optional

User flow

The last piece of the puzzle. User flow is the precursor to the next and final stage of this task -creating a user interface for this app.

Final phase - User Interface design

I’ve immediately jumped onto high-fidelity designs, so, the Lo-fi prototype and wireframes are missed here. After all, some of the constraints when building a new app or system, are actually wireframes. Fast-moving environments need fast solutions and rapid prototyping and quick Candy-like UI is one of them.

The Logo

I’ve made a quicky-simple, and yet (in my opinion) a quite remarkable logo for this coffee shop. I’ve opted for the main color to be yellow, because of its joyful characteristics.

The main screen

Using yellow as the main color and black as the contrast color, the main screen follows the logo style. I wanted everyone who’d sit for the first time in The Caffe to feel the same “offline” vibe when opening the printed menu.Also, I’ve chosen the portrait mode of the tablet, just because (once again) everyone to feel more natural when will “flipping pages” of this digital and modern menu.

Home screen

When the user clicks on the Browse menu, immediately is opened the home page. Here users can find all the products, as well as current special offers.

Categories are placed on the left side of the screen, simply because this menu doesn’t mean to be one-more-mobile-product-Dribbble-app.

Products

The price of the products is mandatory for these kinds of apps, so users can see

that info first. Reviews from other users are presented as stars, and the estimated time for that particular product to come to your table is also presented in the Product Cards. Additionally, the number of calories (if there’s info for it) could be presented there.

Detailed product description

On this screen, users can learn everything about the product. From reviews from the customers, the type of the product (vegetarian, vegan, etc.) to the real story about that product. Ingredients easily could be added and removed, and a really nice addition is the info about the dietary or allergic products. The next step from here is Add to cart, where users can pay for the product, or can continue to browse for more desserts, beverages, and coffee, so they can order later on.

Check out

This screen is known to everyone I guess, as we living in the “Ordering” society. Info about the estimated time of the arrival of the all products is something we don’t see much on ordering pages, so it’s a big plus for customers who are enjoying The Caffe for the first time.Loyalty card feature is presented there as well, whether there are points for some product or discount.

Payment options

So, the final step of the user journey is, of course, payment. Scanning the code, or calling the waiter - offline methods or online methods via Google Pay, Apple Pay, or Card are options that are opted for the users.

One last takeaway

Desing assumptions always will be only assumptions. What’s actually matter is real data, real research and real testing. If our assumptions we’ve felt on our skin, then we’ve achieved so much.

 

Not every digital user is knoweledable about everythig, and not every smart user is the best digital user. Keep in mind on it!

Design process

Goals & Tasks

So, when I find out what the brief is, the next step was to anticipate actual goals and micro-tasks for the users.

User goals:

  1. Learn about free tables
  2. Order immediately
  3. Pay

User tasks:

  1. Search through categories (if there are any)
  2. Filter by price/review/etc. for coffee/deserts/beverages
  3. Pick and order
  4. Choose how to pay
  5. Sent the invoice to the e-mail

Phase one

In this section, I’ve deep-dived into understanding the users by forming and articulating user journeys, user flow, and understanding their priorities and pain points. Personas would be a good addition here, but, since I’ve put all my assumptions about priorities and pain points, I realized that Personas wouldn’t be in so much great favor here.

User priorities:

  1. Find a suitable table
  2. Find a properly brewed coffee
  3. Learn how the coffee is made
  4. Ingredients of the coffee (ratio/percentages/calories...)
  5. Pay with card
  6. Pay with cash
  7. Send invoices by e-mail for better management of their expanses
  8. Make user profile for quick choices (fave coffee/desert, Invoices, loyalty points/discounts)
  9. Use discounts

User pain points:

  1. Trying to find a suitable coffee or desert
  2. Navigating the ordering apps could be a long and painful process
  3. Not sure what ingredients are used
  4. Not being able to find allergic or non-dietary products
  5. Waiting for a long time in line to make the payment
  6. Not seeing a waiter or waitress to wave a hand for making a payment
  7. Not being able to scan the QR code to make an “offline” payment

User stories

User stories helped me to understand context, motivation, and desired outcomes.

  1. Walking through Knez Mihailova user’s attention is getting caught by a huge “kiosk” display with the saying “Welcome to The Cafe where technology meets our present”. Here actually are displayed free spots/free tables which are the main goal for users to step in
  2. Finding the perfect spot
  3. Searching for the best coffee in the town
  4. Want to find all the ingredients in the coffee or desert
  5. Wanna pay immediately
  6. Invoices want always to be sent via e-mail
  7. Want to make a user profile
  8. Faved coffee wanna be ordered quick with one click
  9. Want to pay fast with stored card

User journey

What steps do users take when interacting with the app.

Before, during, and after!

  1. Walks down the street
  2. Seeing big display
  3. Steps in the shop
  4. Finds free table
  5. Scanning really fast the whole app
  6. Finds the categories
  7. Filtering by price/availability/reviews
  8. Looking for the calories
  9. Ordering the coffee/desert
  10. Question about payment
  11. Question if there are any loyalty points or discounts
  12. Choosing payment with Google Pay/Apple Pay or maybe NFC pay
  13. Choosing offline payment (cashier method) *
  14. Choosing call the waiter method *
  15. Choosing invoice to be sent to user’s e-mail address
  16. Clicks okay, returning to the main screen
  17. Picks the order
  18. Enjoying peace of mind time
  19. Continuing walking down the street

* Things should be noted here about offline payment

When users choose offline payment there will be two options

presented - Pay to cashier or Call the waiter

Pay the cashier means that the user needs to scan a QR code or just take a photo of it, then present it to the cashier and proceed with the payment.This is a good option when users don't wanna wait for the waiter or waitress to come by and give them their bill. Quite a fast process, but, there’s always a chance to wait in line for some time.

Call the waiter option is actually made for the old people, or for the users who don't have cameras on their mobile phones. Once the order is done, on the main screen of the device would be visible some kind of sticky message about the payment that needs to be done, and there will be an additional Call the waiter button, which it’s not gonna be presented if a user chose other two options. When the cashier or waiter clicks OK on their devices, that means that the bill is sorted out and the invoice will be sent to the user’s e-mail, of course, if that option is ticked in.

Loyalty card

Before we jump into the Check out and Order options, there’s one thing the user needs to answer - if he/she has a loyalty card or not.If the answer is yes, then users need to fulfill the info, and after that checkout is ready for them with all the discounts which are given as the loyalty card owner.

Mobile app

Web app

Smoodo

Craft. Track. Deliver.

Next project

Mobile app

Verve

Museums. Reimagined.

Previous project

Dejan Zafirovski

Product Designer and Illustrator

Work

About

Let’s work

Phase one

In this section, I’ve deep-dived into understanding the users by forming and articulating user journeys, user flow, and understanding their priorities and pain points. Personas would be a good addition here, but, since I’ve put all my assumptions about priorities and pain points, I realized that Personas wouldn’t be in so much great favor here.

User priorities:

  1. Find a suitable table
  2. Find a properly brewed coffee
  3. Learn how the coffee is made
  4. Ingredients of the coffee (ratio/percentages/calories...)
  5. Pay with card
  6. Pay with cash
  7. Send invoices by e-mail for better management of their expanses
  8. Make user profile for quick choices (fave coffee/desert, Invoices, loyalty points/discounts)
  9. Use discounts

User pain points:

  1. Trying to find a suitable coffee or desert
  2. Navigating the ordering apps could be a long and painful process
  3. Not sure what ingredients are used
  4. Not being able to find allergic or non-dietary products
  5. Waiting for a long time in line to make the payment
  6. Not seeing a waiter or waitress to wave a hand for making a payment
  7. Not being able to scan the QR code to make an “offline” payment

User stories

User stories helped me to understand context, motivation, and desired outcomes.

  1. Walking through Knez Mihailova user’s attention is getting caught by a huge “kiosk” display with the saying “Welcome to The Cafe where technology meets our present”. Here actually are displayed free spots/free tables which are the main goal for users to step in
  2. Finding the perfect spot
  3. Searching for the best coffee in the town
  4. Want to find all the ingredients in the coffee or desert
  5. Wanna pay immediately
  6. Invoices want always to be sent via e-mail
  7. Want to make a user profile
  8. Faved coffee wanna be ordered quick with one click
  9. Want to pay fast with stored card

User journey

What steps do users take when interacting with the app. Before, during, and after!

  1. Walks down the street
  2. Seeing big display
  3. Steps in the shop
  4. Finds free table
  5. Scanning really fast the whole app
  6. Finds the categories
  7. Filtering by price/availability/reviews
  8. Looking for the calories
  9. Ordering the coffee/desert
  10. Question about payment
  11. Question if there are any loyalty points or discounts
  12. Choosing payment with Google Pay/Apple Pay or maybe NFC pay
  13. Choosing offline payment (cashier method) *
  14. Choosing call the waiter method *
  15. Choosing invoice to be sent to user’s e-mail address
  16. Clicks okay, returning to the main screen
  17. Picks the order
  18. Enjoying peace of mind time
  19. Continuing walking down the street

* Things should be noted here about offline payment

When users choose offline payment there will be two options

presented - Pay to cashier or Call the waiter

Pay the cashier means that the user needs to scan a QR code or just take a photo of it, then present it to the cashier and proceed with the payment.This is a good option when users don't wanna wait for the waiter or waitress to come by and give them their bill. Quite a fast process, but, there’s always a chance to wait in line for some time.

Call the waiter option is actually made for the old people, or for the users who don't have cameras on their mobile phones. Once the order is done, on the main screen of the device would be visible some kind of sticky message about the payment that needs to be done, and there will be an additional Call the waiter button, which it’s not gonna be presented if a user chose other two options. When the cashier or waiter clicks OK on their devices, that means that the bill is sorted out and the invoice will be sent to the user’s e-mail, of course, if that option is ticked in.

A smarter way to order

at the café

Designed for comfort,

built for speed.

ABOUT THE PROJECT

The Café App is a tablet-based ordering system that lets customers browse menus, find free tables, and pay, without waiting for staff.

 

I led the full product design—from research and user flows to branding and UI, crafting a seamless in-store experience that blends modern tech with real-world hospitality.

Role

UX/UI Designer

Scope of work

Competitive analysis

Information Architecture

User flows

Prototyping

Logo/branding

Client

the Cafe

Type

iPad app

Timeline

2 weeks

Design process

Goals & Tasks

So, when I find out what the brief is, the next step was to anticipate actual goals and

micro-tasks for the users.

User goals:

  1. Learn about free tables
  2. Order immediately
  3. Pay

User tasks:

  1. Search through categories (if there are any)
  2. Filter by price/review/etc. for coffee/deserts/beverages
  3. Pick and order
  4. Choose how to pay
  5. Sent the invoice to the e-mail

Phase two

This section is all about assumptions, constraints, and eventual trade-offs that were made.

Assumptions:

  1. We can assume that users actually have seen the front-door kiosk display with free-spots-available counter
  2. Users have basic knowledge of how to order from a digital menu
  3. Users have Google Pay, Apple Pay, or NFC-enabled device
  4. Users could pay with cash
  5. Old-aged users don't have mobile phones with the ability to scan QR codes, or don't have phones at all
  6. Users know English. This app could be multilingual (Serbian/English)
  7. Users won some giveaways from social media and now they have discount code/loyalty points
  8. Users want to have user accounts
  9. Cashier service is fast and reliable
  10. The reviewing system is gonna be used a lot

Constraints:

  1. Users can have account profiles, but only created from another device
  2. Only The Cafe tablets should have this app installed
  3. There are three options for payment OnlineCashier serviceCall the waiter/waitress
  4. Invoices can be sent by e-mail with, or without a previously created user profile
  5. Discounts and loyalty points could be given with some kind of loyalty card with its unique number associated with the user. In this case, The Caffe encourage users to have that kind of card and make user profiles and be our loyal everyday consumers

Trade-offs:

  1. Users can create a user account. Users’ top priority is to have a piece of mind time while drinking their coffee or enjoying their dessert. Therefore, there shouldn’t be any barrier to using the app. Without having to create an account, users can interact with the app.Assuming that users, especially tourists can come to The Cafe only once, there’s no strong need for creating a user profile.
  2. Even though I wanted this whole experience to be a fully-digital app with no need for a waiter in terms of paying the bills, a scenario with the old users and those users who aren't tech-savvy was quite possible so I created one more option called Call the waiter.

Phase three

Information architecture

After everything is kinda sorted out, the next step is to create information architecture. Organizing and labeling the content to be easily understood by users, and ensuring its usability, findability, flexibility, and consistency.

Categories

Special offers

Shopping cart

Payment options

Broker

Broker

Main screen

Browse menu

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Product 2

Details

Details

Add to cart

Add to cart

Product 1

Still waiting

Preparing

Coming to you

Beverages

Desserts

Filters

Coffees

Order status

Pay offline

Scan the code

Apple Pay

Call the waiter

Google Pay

Pay with card

NFC-enabled device

Enter loyalty card no.

Optional

Pay online

Call the waiter

Optional

User flow

The last piece of the puzzle. User flow is the precursor to the next and final stage of this

task -creating a user interface for this app.

Final phase - User Interface design

I’ve immediately jumped onto high-fidelity designs, so, the Lo-fi prototype and wireframes are missed here. After all, some of the constraints when building a new app or system, are actually wireframes. Fast-moving environments need fast solutions and rapid prototyping and quick Candy-like UI is one of them.

The Logo

I’ve made a quicky-simple, and yet (in my opinion) a quite remarkable logo for this coffee shop. I’ve opted for the main color to be yellow, because of its joyful characteristics.

The main screen

Using yellow as the main color and black as the contrast color, the main screen follows the logo style. I wanted everyone who’d sit for the first time in The Caffe to feel the same “offline” vibe when opening the printed menu.Also, I’ve chosen the portrait mode of the tablet, just because (once again) everyone to feel more natural when will “flipping pages” of this digital and modern menu.

Home screen

When the user clicks on the Browse menu, immediately is opened the home page. Here users can find all the products, as well as current special offers.

Categories are placed on the left side of the screen, simply because this menu doesn’t mean to be one-more-mobile-product-Dribbble-app.

Products

The price of the products is mandatory for these kinds of apps, so users can see

that info first. Reviews from other users are presented as stars, and the estimated time for that particular product to come to your table is also presented in the Product Cards. Additionally, the number of calories (if there’s info for it) could be presented there.

Detailed product description

On this screen, users can learn everything about the product. From reviews from the customers, the type of the product (vegetarian, vegan, etc.) to the real story about that product. Ingredients easily could be added and removed, and a really nice addition is the info about the dietary or allergic products. The next step from here is Add to cart, where users can pay for the product, or can continue to browse for more desserts, beverages, and coffee, so they can order later on.

Loyalty card

Before we jump into the Check out and Order options, there’s one thing the user needs to answer - if he/she has a loyalty card or not.If the answer is yes, then users need to fulfill the info, and after that checkout is ready for them with all the discounts which are given as the loyalty card owner.

Check out

This screen is known to everyone I guess, as we living in the “Ordering” society. Info about the estimated time of the arrival of the all products is something we don’t see much on ordering pages, so it’s a big plus for customers who are enjoying The Caffe for the first time.Loyalty card feature is presented there as well, whether there are points for some product or discount.

Payment options

So, the final step of the user journey is, of course, payment. Scanning the code, or calling the waiter - offline methods or online methods via Google Pay, Apple Pay, or Card are options that are opted for the users.

One last takeaway

Desing assumptions always will be only assumptions. What’s actually matter is real data, real research and real testing. If our assumptions we’ve felt on our skin, then we’ve achieved so much.

 

Not every digital user is knoweledable about everythig, and not every smart user is the best digital user. Keep in mind on it!

Web app

Mobile app

Smoodo

Craft. Track. Deliver.

Coming soon

Mobile app

Verve

Museums. Reimagined.

Previous project