The edible live streaming community





What were the problems you were hoping to solve? How did you learn about the problems? Were they hunches, or already validated through testing?

  • I wanted to go through the entire design process and incorporate more UX research and testing. I seized on an idea my friend had about a Twitch-like streaming service focused. I fleshed out the idea a bit and conducted a survey about food, streaming, and the concept. I also casually had conversations with close friends and family.


Only 1 person working on the project. Able to bounce ideas, test, and get feedback from a lot of people. But ultimately one person did everything on this project.

  • Material Design limits how creative you can be with your design.

  • Business constraints are things like timeframe to meet a promised deadline (last week?), budget or resources allocated for the project, and the size of the team (uh, did you even have a team?) dedicated to the project. Every company has plenty of these.

    • I didn’t have any budget for this project, so I was constrained to the software I already have, trials of new software (Protopie, Talebook) and doing testing on my own (most of the UX testing software was extremely limited or expensive [Usability Hub]). I also found that such software wasn’t needed for a small project that was built from scratch.

  • Technical constraints are things like having to use pre-existing codebase/ style guides, being confined to a specific device like iPhone application, or even “we have to support IE7”. When designing for an interactive medium, the technical constraints play a hefty role in how we approach the design.

    • Being confined to Material Design and android, which I hadn’t designed for before. I didn’t even have an android phone to test my designs in real life on along the way. That was a major mistake that I would change next time.

    • I didn’t have a developer or development process planned out ahead of time, so I didn’t have a specific development protocol to follow while designing. Generally, I started from the smallest widely-used android viewport, created screens for tablet, followed an 8px grid, and 2 column layout. Layers were named logically and shadows, fonts, colors for the style guide were organized and adhered too.

    • A lot of technical challenges, workaround, and hacks had to be created for this project because I used a whole host of softwares that aren’t necessarily made to work together smoothly. I like the challenge of trying new softwares (because there are an abundance of them in the design ecosystem), but next time I would try to use a software that encompassed the ability to wireframe, design, prototype, and animate all together. Figma is definitely a new favorite of mine because everything is based in the cloud.




March - April 2019 (2 months)


Research, Branding, Design, Animation


Persona, Journey Map, Sitemap, User Flow, Style Guide, App Screens, Interactive Animated Prototype



What was the initial problem?

  • Where can I watch live streaming about food?

Realized that a food streaming app wasn’t viable. Shifted to focusing on following through on the entire design process for a concept.

  • Shifted to focusing on creating a Twitch replica where anybody could stream their food content to a community where restaurants streamed their kitchens while consumers watched, followed their recipes, reserved seats with them, awarded them stars, or asked questions with credits. I thought allowing just anybody to stream cooking would lower the quality of the platform, so instead there is a verification process whereby we check if you’re an actual restaurant before you can stream. You get a restaurant profile, everyone else gets a user profile.

  • There is a social aspect where you can follow users or restaurants. You can talk to other users. You can ask questions of restaurants with credits on their stream.

  • We focused on our persona, Tia, and her main task: making a reservation.

  • Food is big business. Food choices and niche consumers (diet, craft, etc.) are expanding. Companies, restaurants, consumers all need a space to interact. There are cable food channels and generic streaming services. But where can one tune into and interact with exclusively food 

Food is big business. Users want to learn from professional chefs, but current cooking shows are slow and without interaction and live streaming services don’t focus on food-related content. Restaurants want to connect with new customers, but rely on word-of-mouth and unpredictable reviews. Where can one watch and interact with chefs and recipes live?



Create a mobile food cinema that is easy to watch and interact with. Create a new platform for restaurants to reach customers and showcase their kitchen, talent, and food. Entertain and inform users. They can learn new recipes, cooking techniques, and about local restaurants.

  • Why was the product successful?

    • 1-3 rating for users completing tasks went up over the course of testing different prototypes

      • Went from lots of 1-2s to mostly 2-3s.

  • Business model for CHEW

    • Nom failed

    • Get money from people paying for “question credits” to ask restaurants questions live. Similar to people paying Twitch for bits

    • Restaurants/food companies pay to advertise.

Value Proposition

Solution: Companies get a new way to reach users interested in food. Users get an interactive way to learn about food, recipes, new restaurants, and showcase their cooking talent.

CHEW will provide a platform for both users and restaurants to reach each other via live interactive streaming. Users will learn about new restaurants, foods, recipes, and cooking techniques. Restaurants will connect with new clientele and showcase their location, menu, cooking style, and talent.





Paper & Pen, Sketch, FlowMapp, Overflow, Figma, Protopie, Adobe Photoshop





Survey was too long, too many questions. Didn’t give great data. In-depth interviews would’ve been better.



Who did you speak to about the problems? Who did they impact? Did you define use-cases? Did you find patterns of users (e.g. personas) after talking to them? Were you not able to talk to any users?

  • I surveyed younger international people from the designer community. They gave me a perspective that a food streaming app probably wouldn’t be used much. I did find a pattern of people who are health conscious and tech savvy wanting to try a product like that. I defined a persona and use case (reserving a restaurant) based on that.

Shared Talebook survey with friends and groups on Facebook.

🍗 Hey UI & UX folks! 🍎

I'm doing a bit of research for a food-related product! If you have a minute, would you mind answering a few questions at the link below? https://goo.gl/V6GyN4


Survey Data

  • Age - Late 20s

  • Location - Atlanta, GA

  • Job - Student, Personal Trainer

  • Tech savvy

  • Likes messaging, social media, and news websites.

  • Likes social media, email, and map apps.

  • Only one person uses a food-related app. Indian person who uses Tomato.

  • Most people don’t watch live streaming. Those that do watch, Twitch (2), Youtube (2), Facebook (1), and NASA (1).

  • More people than not didn’t like being on camera. A little shy for streaming perhaps?

  • Most people post online and contribute. They seek to interact with their content.

  • Italian (3), Japanese (2), Asian (4), Arabic (2) were the most popular foods.

  • Most people didn’t have food allergies. Some were pescatarian, prawn, spicy, no pork.

  • Most people ate out multiple times a week. Some only a few times a month.

  • People like to try new restaurants if they do eat out. Happens typically once or twice a month.

  • People use social media (facebook, instagram, youtube), Google reviews, and friends to find out about new restaurants. Especially friends. Only one person said they used Yelp (a food app).

  • Most people like to cook.

  • Most people like to watch others cook.

  • People watch cooking on Youtube (2), Chef’s Table (3), cooking shows (4), Netflix (3).

  • People want to try Japanese (3), Arabic (2), Asian (3), and African (2) food.

  • People generally don’t care about the name brand. If they do, it’s a fast food (Dominos, Pepsi, KFC, McDonalds) or health food (365, Yves, Wellness Warehouse)

  • People learn recipes by Google (5) or experimenting (4). Not a fan of traditional recipe books. Young people aren’t going to open book and follow a recipe. Only 2 people in the survey said they did this.

  • People learn about a new recipe from friends, social media, Google.

  • The hardest part of cooking is timing (3), ingredients (5), and cleaning up.

  • People of this age generally don’t visit food websites regularly. If they did, it was Pintrest, NYT cooking.

  • People don’t use food apps. Pinterest, Kitchen Stories, Zomato, Food panda.

  • People weren’t crazy about food streaming. They might try it (7) or no (6).

  • People thought someone would use this app if they were a foodie, keen on cooking, wanted to learn, and interact with professionals.

  • People thought someone would use this app if they had lots of free time (2), loved cooking (4), older women, middle aged people who like cooking shows, food enthusiast, mothers, food aware and tech-savvy.

  • People wouldn’t use it if it’s difficult, they just want the recipe or the food without the hassle. They are too busy and would rather interact with people IRL while cooking.








YouTube Cooking Channel

Facebook Live


Twitch Food

Competitive set: screenshots and page examples of other competitors

Competitive audit: taking one of those pages and pointing out good parts, bad parts, etc.






Vegans, vegetarians, organics, foodies, young audience, people who eat out often.

  • What problems did you think you were solving for them?

    • A new way to learn about local restaurants.

    • New recipes that she can follow along with via video instead of reading out of a cookbook.

    • A platform to interact with chefs/restaurants and ask questions (because she’s health conscious) before reserving a seat there.

  • Is this a small niche of people, or half the world?

    • Our users could be anyone who enjoys watching cooking. However, our target audience is a younger, tech savvy and foodie group who would utilize a stream to learn more about their food or local restaurants.

  • How does the tech you work with influence their lives?

    • Tia uses her phone, like most millennials, for every aspect of her life. Workout routines, calendar, entertainment, etc.

Initial Persona

  • Young vegan/vegetarian/foodie comfortable with streaming platforms who looking for food entertainment and ideas.




Flow through the product based on persona with 2 common use cases

  • New Restaurant

  • New Recipe




Information architecture is mapping out all the paths a user can take on your product/website to different destination key points.





Create user flow for journey map goal/task that my persona user would complete

  • a visual representation of the path the user can follow to achieve a goal.

  • Having this representation helps you reflect on the user’s flow, communicate it and get feedback. You can see it better yourself, but also your team and stakeholders can see, understand and provide input.








Purple and bright turquoise.

Why the purple color? The color should fit with your “ideal user” or persona. Afterthought: I picked purple only because it was a different color from my other case studies (green and blue). I also picked it because it somewhat matched Twitch, which most other streamers are used to. If I don’t want to change the color, I could legitimize it by saying the dark purple is a “royal” or “high-end” color to make the service seem high quality. Also, this app is like a “food cinema”. We want dark colors like the interior of a cinema so users focus on the streaming and video features. The dark purple fits this while also being more characteristic than black.




  • Has many weights. Common web font that is readable at large and small sizes. Works for all app and pages.

  • The only other typeface I used was Phosphate Solid for the CHEW text. Make it look large, thick, and almost “chewable” like a big steak or gummy.



Two-tone Material Design icon set





3 rounds: 1-2 about screen logic and features, 3 about design and aesthetic elements

For your initial solution exploration, what did you come up with? Did you define success goals with your potential solution? How’d you decide to explore these paths?

  • I created paper wireframes for my initial solution, made an InVision prototype, then tested it with 4 people. I created a task list that my persona and use case would need to accomplish, and ranked (1-3, 1 being worst, 3 being best) how each tester completed the task. Had 1 unstructured testing for each round. Then I focused on specifics issues that were mentioned/repeated with each tester and I focused on tasks that scored low (high difficulty) overall.

What did you sketch? How did you sketch? Mockups? Did you need to devise any sort of patterns, e.g. style guide, UI pattens, or brand guidelines? Show examples.

  • Sketched on paper with pen. Used a mobile frame and follow material design patterns while using the branding I had created a mock landing page for CHEW. I also looked for inspiration from other food apps, material design apps, and patterns/styles I liked from around the internet (Medium, Dribbble, etc).












Issues navigating to certain pages.

  • Reservation

What did you learn from the tests? What surprised you about the results?

  • It surprised me how quickly users moved through the wireframe (which was so simple and poorly drawn). They understood the basic logic of a mobile app and of material design’s look. The key here was to not to stray too far from these tried-and-tested looks for the sake of creativity at the cost of the user’s ease of experience. 

  • Also, people just liked to click around a mobile app without really thinking… even without a goal in mind… and especially when they didn’t know where to go. They just liked to explore.

  • It surprised me how hard it was to find certain features and pages that I thought were obvious. This is where having an outside perspective on something you spent hours designing and staring at is really useful.

Flow logic

  • People really like to just click, click, click, click without thinking about what they are clicking. Especially if they are confused and don’t know what to do. They do this especially when they first enter an app to explore. It’s almost like a dog sniffing out his territory before he relaxes. It’s human nature to explore mindlessly I think.

  • I have each prototype (InVision, Figma, InVision, Prtotopie) along the way. Link each one? Showcase selected screens from each prototype? Have GIFs showing changes for selected screens?

Check if aligns with UX research and persona

The Nielsen Norman group recommend testing with no more than five users at any one time. Multiple tests with <5 users are ideal. There are diminishing returns with larger numbers of users.

Unstructured test and task test

Write out list of tasks, actions, use cases, user flows.

  • Ask user to perform each task.

    • If the user can perform them quickly and with no trouble, mark it a 3.

    • If the user can perform it but has some struggles, mark it a 2.

    • If the user can’t perform it, mark it a 1.

  • Ask 5 different users to perform these tasks, add up the numbers, and start working on the lowest scoring behaviors first.

Sit down with prototype next to user

  • Give them brief introduction and show them the product

    • Explain to them that you are going to show them a product and you want them to use it and speak aloud what’s going through their mind at all times.

  • Ask them:

    • What’s going through your head as you look at this?

    • What do you think you can do on this page?

    • How would you do that?

    • What are you thinking?

    • What do you think would happen?

Tasks (5)

  • *Check your Profile

  • *Watch a Stream

  • *Make a reservation at a restaurant

  • *Send a message to a friend

  • *Change a setting

  • Message a Friend

  • Check Notifications

  • Sign Up

  • Filter Stream options

  • Message person hosting live stream

Unstructured Test

  • Introduction 

    • I will show you food live streaming app. 

    • I want you to walk me through how you would use it by speaking and clicking.

  • Questions

    • What are you thinking?

    • What do you think would happen?

    • What do you think you can do on this page?

    • How would you do that?

Task Completion Test

  • Introduction 

    • I will show you food live streaming app. 

    • I will give you tasks to complete.

    • I want you to walk me through how you would do it by speaking and clicking.

  • Tasks

    • Change your profile picture

    • Watch a stream

    • Make a reservation at a restaurant

    • Send a message to a friend

    • Change your settings

    • Filter the streams by Japanese food

    • Pick a restaurant from the map

    • View a restaurant’s profile

    • Create your own stream

    • Find a restaurant’s recipe

    • View your reservations

  • Rating

    • If the user can perform them quickly and with no trouble, mark it a 3.

    • If the user can perform it but has some struggles, mark it a 2.

    • If the user can’t perform it, mark it a 1.

Are the user’s goals being met?

  • Are actions available for user?

  • Are the user’s frustrations dealt with?








Use Figma’s smallest default “Android” dartboard (360 x 640)

4dp baseline grid

8px grid

48px x 48px tap targets

  • 40px between adjacent tap targets

  • 65 characters per line (65 cal) is ideal length of text

  • Minimum mobile body (reading) text: 16px size / 1.2em line height

  • Magic number is 8 (elements sizes, spacing, fonts, etc.)





What features are most important to have.

  • Difference between friends, following, followers?

  • GO LIVE button. Reserve button. Recipe button.

  • Question credit

  • Reminder button

  • View recipe

  • Go LIVE verification process

  • Make on boarding pages simpler

Major features

  • What is the best way for a user to ask a direct question to the chef without being lost in all the comments and noise?

    • A credit system where you get 1 question credit per day (unless you pay for more) to ask a direct question to the streamer. It bypasses all the other comments and stands out for the streamer. Is it a separate list (comments and questions) or does it just visually jump out on the screen? I think it needs to be on a separate list so that if the streamer is cooking and comes back to the screen they see it and can address it.

  • How will a user get recipe details? Sure they can watch a stream… but what if the streamer didn’t detail their recipe or go into measurements.

    • The streamer could attach a recipe document to a stream before or once completed (shows up under restaurant profile for past videos). There our user could open and use it while referring to the stream while cooking.

  • Rating is attached to the user or profile. Connected to how many “thumbs up” or lets call them Michelin or CHEW stars you receive on your live streams. So nobody is poorly rated, there is just higher and lower rated people based on stars.

  • Section at top of discover page to recommend the latest or newest restaurant. Featured or recommended section/tile based on newest restaurant or what you selected to be recommended.

  • How to show an upcoming stream vs a current stream vs an old stream

  • Button to save/follow/remind you about upcoming streams





Scroll, drag, active state, error state, button tap, screen transition, pop ups, loader, splash screen

What is most important?

  • Big blue fab buttons.

  • Play button on stream cards

  • Buttons (purple or blue) to click on each page

  • How do the layers work?

    • Menu page is on top.

    • Everything within the menu slides out on top of home plane.

    • Top right filter button pages are on top.

    • Video and content comes from bottom. 

    • Messages and following are on same plane as home.

  • What is my brand’s expression?

    • Exotic, quick-paced, quirky.

Add loading time/animation to when you input your stream verification information

  • Explain in case study that providing fake loading time makes a user feel that the app is working better.










What was the final result? How did it get made? How did you measure its efficacy? Did you measure success?

  • The final result was 49 mobile screens created in Figma that were organized/named and ready to be handed off to a developer. Additionally, I had an animated interactive prototype made in Protopie to share to illustrate the intended animation and flow of the screens. And lastly, a branding guide and tentative tablet and web screens if the app was to be fully designed and developed for other platforms.

We’re success metrics reached?

  • 1-3 rating for users completing tasks went up over the course of testing different prototypes


How did the problem shift as you worked through the project?

  • Realized that a food streaming app wasn’t viable. Shifted to focusing on following through on the entire design process for a concept.

  • Shifted to focusing on creating a Twitch replica where anybody could stream their food content to a community where restaurants streamed their kitchens while consumers watched, followed their recipes, reserved seats with them, awarded them stars, or asked questions with credits. I thought allowing just anybody to stream cooking would lower the quality of the platform, so instead there is a verification process whereby we check if you’re an actual restaurant before you can stream. You get a restaurant profile, everyone else gets a user profile.

  • There is a social aspect where you can follow users or restaurants. You can talk to other users. You can ask questions of restaurants with credits on their stream.

  • We focused on our persona, Tia, and her main task: making a reservation.

What problems arose?

  • How to export design from Figma to software that can animate and embed an interactive prototype on the web.

    • Tried InVision, InVision Studio, Adobe XD, Principle, Figma, and finally Protopie.

    • Protopie-Figma integration was in beta, so there were lots of import issues to adjust.

    • Custom HTML/CSS had to be used to embed a presentable prototype.

  • Doubts about product idea and business model. 

    • Business model and product (Nom) has already been created and failed (2016-2018). It was well funded, organized, and launched with support from many celebrities and chefs. Founded by cofounder of YouTube.

    • Young people who watch streams don’t watch cooking.

    • Learning cooking while watching too difficult.

      • Dirty/wet hands from cooking while handling technology

      • Watching entire stream too slow; people want just the food or recipe.

    • Do technology and food really fit together? 

      • Let’s say a chef is cooking. If he is streaming from his phone with the back camera of his phone. How will he know what’s going on with his viewers? What questions they are asking? He would have to stop cooking and go around to the front of the phone to respond. Doesn’t make sense. I had this same thought early on in the market research process: technology and kitchens don’t mix. You don’t want to be using your phone/computer/camera around water, fire, food. Stopping to wipe your hands off to type of fix something on your computer wouldn’t make sense while being focused on cooking.

    • People want quick recipes and entertainment, not watching the whole cooking process on a stream. Don’t want the hassle. Would rather interact with people IRL. They weren’t crazy about the idea of food streaming.

    • Why use this service instead of Twitch, Facebook, Youtube, etc?

How did the problem change as you learned more? How did you adapt (iterate, refine, pivot) the solution as you learned? Which of your most precious ideas did you kill off in the process?

  • I changed the main concept of the app from a streaming service for all to a streaming service for only restaurants. I added major features (recipe, reservation, question credits) to align with this. I had a lot of feedback on changing the color and the font, but after much testing… I decided to stick with my gut feeling. 

  • Simplified onboarding process.

How did you decide you were finished? Was it a clear marker, or did you have to make a tough call?

  • You can keep iterating, fixing, changing, and adding forever. You definitely have to do your due diligence with regards to testing, iterating, and then call it when it feels right. I wanted to call it when I was done with my animation, but realized if I was going to test every other stage of my project, then I had to test the animation as well.

How did you feel at different parts of the project? When were you most excited? When were you most frustrated?

  • I enjoyed the user testing (enjoyed talking to people and watching them “unbox” the product and run into issues and make note of them) and animation (fun, great to see everything finally come together into a realistic product).

  • I disliked starting the project (hard to get rolling and know where/how to begin) and being stuck with so many options/iterations/issues deep into the design step.


Dealing with designer’s block

This is the longest design process for a product that I’ve yet tackled. Throughout that process, there were days where I really hit a “block”. Where I got lost in the minutiae of the present problems and variables and lost sight of the big picture. This especially happened during the initial research phase. I’m primarily a designer, so I often would get frustrated with trying to write about the product, business model, or user needs and think––I should just jump to the design stage. What am I doing wasting my time here if the point of this entire exercise is to design an app.

This is where starting with a clear sense of overall direction/goals/purpose really helped. I could glance back at my outline of my workflow and know that my current predicament had a purpose in the grand scheme. That the process was a marathon, not a sprint. A night of sleep or a new user would give me a fresh perspective that would allow me to find a solution to the problem and push forward to the next task. Additionally, having the focus of one persona (average user) and one journey/task (average goal) during the design phase was key. There is a laundry list of potential features, pages, solutions that could be added to the app, but framing these in the context of what would be best for my persona helped me strip away the crap and design only the essentials well.

What would do differently?

  • She suggested it was better to start with 5 qualitative user interviews then do user surveys then create a persona based on this information. I shouldn’t rely too much on information from surveys because these person are really motivated and enthusiastic about the product/idea or about helping you. Not an average user.

  • “How do you choose to do interviews or a survey first?” It depends on the product. On a startup, in a new field, its better to start with qualitative interviews. On a more well known product/field, a survey is better. Ultimately though, you will have fans of your product filling out the surveys, which can bias it. People will talk more in an interview than in a survey, which can allow you to get more in-depth data and insights. Offline, in-person interviews are better to gauge feelings, emotions, and problems. Easier to design for someone you really know. You don’t “feel” or “see” the pain points with a product from a survey response.

  • “How do you pick your users to interview?”

  • She decides who to interviews through a “screening” process.  Check your competitors and see who is using those products. Or based on rough picture in your mind, ask on Facebook or some group if anyone is interested in your idea or for an interview. You build potential users for the future when your product is complete.

  • I didn’t even have an android phone to test my designs in real life on along the way. That was a major mistake that I would change next time.

Should you have spent more time talking to users?

  • Not overall. I tested and surveyed users well. However, I should’ve started the entire research process with a couple of in-depth user interviews (see Anika’s suggestions).

Should you have spent more time exploring concepts?

  • I could’ve done some A/B testing on certain pages instead of just relying on my judgment. However, this is a brand new product… a/b testing is better for established products where a small change can make a big difference to a large user base.

  • I could’ve explored more branding concepts initially (colors, fonts, logos) instead just going with my purple landing page. By the time I got feedback to change those colors in the 3rd stage of testing, I was already too invested in them and couldn’t see changing them to anything else.

Did you stumble in setting expectations or communicating with your team?

  • No communication problems. I did a great job user testing. My surveys could’ve been simpler and had more specific questions.

  • I wasn’t sure about how to set goals and success metrics and measure success at the end. How do I do this on personal project that isn’t developed or sent to real users? My goal was to create a portfolio piece… any other “goal” was really more of my solution to the problem. I felt “successful” in the end because I completed it at all, and it was a long project, and was happy with how it looked.

Throughout a successful project, you’re going to have to prioritize. This means saying “no” many more times than you say “yes”. Recall those decisions, and pinpoint where you would have gone next if you had more time or resources.

  • Future pages and features that I said no too.

  • Including more animations that aren’t possible in protopie (button flash) and I didn’t have time for (keyboards popping up, active/error states, input layers).

  • Thoroughly designing an entire tablet and web product.

  • Designing for iOS mobile and tablet.

Not all projects are successful; this is ok. The team can fall apart, the project can fail to get traction, the client can run out of time or cash, you may solve the wrong problems or spend too much time going down the wrong path, etc. Talk about one of these problems.

  • Ultimately, my goals were completed with the project. However, along the way I realized that bring a real product like this to market (even if I wanted to) wouldn’t make sense. The survey suggested that people weren’t really into a food live streaming app. That the product had already been tried (Nom) with way more resources and backing and failed. That the realities of using food and technology at the same time didn’t make sense. But this is okay, because for me it was more about the design process than if the product or business model was viable.

Future Features

Future improvements

  • What would complete this app?

    • Error page

      • When you click a feature that isn’t created/implemented/ready.

      • Empty dinner plate/bowl.

      • Quiet kitchen

    • Report button

    • Report button page

    • Social share icon dropdown

    • Settings pages

    • Profile page edit page

    • Other restaurant profiles

    • Other user profiles

    • Scrolling on home live/upcoming/videos pages

    • Other stream pages

    • Stream dashboard

    • Go LIVE stream page for recording

    • Reservation edit page with delete/cancel button

    • Followed restaurant profile page

    • Add follow user profile page

    • Other filter pages with background for map/upcoming home/videos homes.

    • Other menu pages with background for rest of app.

    • Other menu pages with different part highlighted.


CASE STUDY: Starter Pack – Life Improvement (Web)

CASE STUDY: Starter Pack – Life Improvement (Web)

CASE STUDY: Move - Ride Share (Mobile)

CASE STUDY: Move - Ride Share (Mobile)