Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
74 views9 pages

Team Munch Case Study

Team Munch is a web application that allows team members to individually choose meals that are then aggregated for a group lunch order. The biggest challenge was designing user flows for when the team leader pays versus individual payments. Cookies and the Hapi framework helped determine the correct user journey through the use of templates that generated personalized messages and screens for each user type.

Uploaded by

Loava PAtti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
74 views9 pages

Team Munch Case Study

Team Munch is a web application that allows team members to individually choose meals that are then aggregated for a group lunch order. The biggest challenge was designing user flows for when the team leader pays versus individual payments. Cookies and the Hapi framework helped determine the correct user journey through the use of templates that generated personalized messages and screens for each user type.

Uploaded by

Loava PAtti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Summary

Team Munch is lunchtime delivery web application that allows people to choose their meals
individually in a team and the payments are aggregated.
Challenge
The biggest challenge was understanding how the user flow would work. We had two different
user journeys - either team leader pays or team members pay. Depending on whether you were
a team leader or a team member and whether the team leader was paying or not, a user would
only see certain screens. The challenge was making sure the user was directed through the
correct user journey.
Solution
The use of cookies, the Hapi framework and the handlebars templating engine helped us
overcome the challenge of determining the correct user journey for the user. Cookies allowed
us to easily check through Hapi what type of user they were and at what part in the user flow
they needed to be at. Handlebars allowed us to reuse the same HTML pages but generate
different messages on the page according to what type of user they were.
Technologies
 Hapi
 Stripe API
 Redis
 Bootstrap
 jQuery
 Handlebars
Screenshots

You might also like