Product Case Study – Starbucks (Online)

As a Product Manager of this app,

outline the technological difficulties you foresee?

• Building an UI/UX which matches the quality of a native mobile app

• Handling of complex business logic like customization of menu, location wise prices

• In order to create the offline functionality for the PWA, complex caching had to be set up to download the information for each menu item, store information on customers’ previous orders, and store static pages from the website. set up the server so it could handle in-memory caching and efficient server-side rendering.

• Performance & Speed: Is unlike native apps that are developed and optimized for a certain platform and provide a high level of performance.

• Feature restrictions. There are some features that PWAs can’t use. For instance, PWAs have no access to calendars, contacts, browser bookmarks, and alarms. Moreover, a PWA can’t intercept SMS or calls, get a user’s phone number, and so on

• Limited web browser support. PWAs are not supported by all web browsers

• No consumer data. As compared to native mobile apps, PWAs generally have no access to consumer data such as contacts and social profiles

• Limited iOS features. With PWAs, push notifications aren’t available for iOS users.

• Navtive apps can better integrate with other apps.

• Geofencing is not available on PWA

● Define vision

As Starbucks is an everyday product for most of their customers, we are aiming to make ordering and payment convenient to reduce the time the customer spends on getting an item from the menu.

• Define the business objective

  ❖ Improve digital engagement
  ❖ Faster Execution of orders
  ❖ Higher Sales
  ❖ Increase customer loyalty
  ❖ Less dependency on physical stores
  ❖ Reaching out to customers across geographical locations

• Define who the users are (User Personas)

  ❖ Salaried employees with a 9-5 job – Tend to pick up one beverage in the morning.

• Freelancers – Working from the cafe

• High end executives – Frequent indulgences in the beverage(s)

Define the customer pain points (Customer interviews, surveys, app reviews)

• Wireframes, Prototypes

  ❖ Home Screen
  ❖ Menu Screen
  ❖ Order Screen
  ❖ Payment Screen
  ❖ Store locator screen

  ❖ Gift Card Screen

  ❖ Offers Screen
  ❖ Zero State screens wherever applicable

• Detailed PRD

  ❖ Purpose
  ❖ Features
  ❖ User Flow
  ❖ User Stories
  ❖ Release Criteria

  ❖ Timeline

  ❖ KPIs

Give a brief overview of the tech stack you would envision for this app.