Flow / User Journeys / User Stories

[Joepock123]

Issue: #3
HackMD user flow markdown here.
Inspiration from Kristina

Important links

Google Maps API - heatmaps
Customer Survey Data
Ice Cream Truck Finder Product Development Statement - Google Doc

---

Flow 1 - ICE CREAM VENDOR

Main User Journey

1. As a vendor, I want to find potential customers so I can sell more ice cream in my area.

Supporting User Journeys

1. As a vendor, I want to upload my route locations so customers can find me.

Main Flow

1. Page 1 - Landing page, option choice between vendor/ customer (choose vendor)
   • Intro to app? Image? Or animation of truck/ice cream logo moving on map
   • Header/footer?
   • Vendor/Customer Button
2. Page 2 - Only see if not logged in - option choice between login/ signup
   • Choose either option
   • Design wise, this will be similar to the first page
3. Page 3 - Only seen if not logged in - Signup form
   • Name, password, email saved to database via submit button
4. Page 4 (could combine with Page 3?) - Only seen if not logged in - Login form
   • Page will display password, email fields and a submit button
   • This will be checked against a database
5. Page 5 - Dashboard - Previously saved schedule, settings
   • If no previous schedule (i.e. first time logging in) will be an empty schedule
   • Three buttons
     • Edit Schedule (route expiry: dates/time/default 1 week?)
     • Clear schedule for today (meaning they're not working)
     • Turn alerts on for heat map spikes nearby (could use switch buttons)
6. Page 6 - Edit Schedule - Form
   • Time starting, time finishing, address
     • Submit button - back to page 5
   • Copy another schedule (from database)
   • Route expiry?
   • Save route for another day? (to database)
7. Page 7 - Heat map
   • Google Maps API - heatmaps
     • Based around their route
     • Heat map in theory should show clusters of customers who want some ice cream from a X mile radius from which point the ICV is in their route (need to discuss what the max radius will be and if we're displaying this in miles or km)
   • Button link
     • Back to dashboard
     • Edit schedule

User Stories

Accessibility

1. As a user, I want a clear understanding of how to navigate the website
2. As a user, I want this site to be accessible to people of all abilities
3. As a user, I want a way of moderating content before it is posted publically
4. As a user, I want to be clear about copyright laws/infringement otice when adding information
5. As a user I want to be able to edit and delete my data

Content

1. As a vendor I would like to be able to input text so I can sign up and login. [0.5]
2. As a vendor I want to be able to see all of my available options (dashboard) [1.5]
3. As a vendor I want to be able to edit/update my route and timings. [1.5]
4. As a vendor I would like a visual representation of my route
   • In a flow chart [1.5]
   • On a map [1.5]
5. I would like to import my route into Google Maps so I can use directions [3]
6. As a vendor I want a visual representation of demand of customer demand for ice cream
   • For today [2.5]
   • Historically (last 1 month/1 year) [3.5]
7. As a vendor I want an option to show potential customers that I am unavailable for the day [1]
8. As a vendor I want to be able to choose what alerts I receive [2]
9. As a vendor I want to be able to easily replicate previous routes [1.5]

---

Flow 2 - ICE CREAM CUSTOMER

User Journey

1. As a customer, I would like to find out when an ICV is coming to my area / demand one if there isn't any.

Supporting User Journeys

1. As a customer, I would like to see product information about vendors

Flow

1. Page 1 - Landing page, option choice between vendor/ customer (choose customer)
   • Intro to app? Image? Or animation of truck/ice cream logo moving on map
   • Header/footer?
   • Vendor/Customer Button
2. Page 2 - Only see if not logged in - option choice between login/ signup
   • Choose either option
   • Design wise, this will be similar to the first page
3. Page 3 - Only seen if not logged in - Signup form
   • Name, password, email saved to database via submit button
   • Check box for "Are you okay with us taking your location?" (required) - does this meet GDPR regulations???
4. Page 4 (could combine with Page 3?) - Only seen if not logged in - Login form
   • Page will display password, email fields and a submit button
   • This will be checked against a database
5. Page 5 - Map (location taken from device information)
   • Map with ice cream location (default 500m then can select 1km, 2km etc)
     • STRETCH GOAL: Link to ice cream man page for each vendor
     • STRETCH GOAL: Filter ice cream men (vegan etc)
   • button - (to signal interest to ice cream vendors) - saves to customer location database, deprecates after 30mins. - links to caution modal
   • N.B have to be clear what bring me ice cream button does (how likely am I to see a van, am I contacting anyone directly? How will this be of use to me in the immediate future?)

User Stories

Content

1. As a customer I would like to be able to input text so I can sign up and login. [0.5]
2. As a customer, I want to be able to sign up quickly so I don't waste any time since it's just ice cream [0]
3. As a customer I would like to automatically take my location from my device information so I do not manually have to input my postcode [1]
4. As a customer I want to favourite ice cream vendors so I can see where they are [1.5]
5. As a customer, I want to see the closest ICVs and instructions so I can make an informed decision how to get there. [2]
6. As a poor customer with no nearby vendors I would like to alert them that I'm willing to part with $$$ so they come to my area [2]
7. As a customer who made an alert I'd like information on when I will receive my ice cream [3]

Accessibility

Technical Goals

Database schema

1. User db
2. Routes db
3. Locations db for where users have clicked

Google Map API & Data Visualization

1. Create a heat map
2. Display useful data to vendors regarding demand
3. Provide feedback to customer what happens after use alert