Android Studio, Firebase, Google Maps API, Volley
DORMDASH
CONTEXT
As a college student, eating real food is hard.
We're tight on time and money. Sometimes the walk from the dorm to the cafeteria is 20 minutes or more, in which case we'd default to a granola bar.
​
Perhaps students need a cheaper, more efficient deliver service, one that suits the needs of college students in particular.
# Respondants: How much are you willing to pay for on-campus delivery?
INITIAL RESEARCH
First, we determined whether such a service would be of interest.
​
Through a survey of students from Cal Poly Pomona, USC, and UC San Diego, our team found that distance has a huge influence on cost: customers were willing to pay 2x more on campuses like CPP and UCSD versus USC. As expected, the average price a student was willing to pay was lower than the cost of established services like UberEats or Postmates.
$
1
​
2
3
​
4
5
"More than 5"
40
30
20
10
USC
UCSD
226 acres
1200 acres
Cal Poly Pomona
1438 acres
UberEats
Grubhub
OUR SOLUTION, EXPLAINED
We designed this interface to resemble existing crowdsourced delivery apps like Lyft and Uber, featuring a map. Because delivery and pickup points were projected to be within walking distance, we provide a path on the map.
​
​
This not only creates subconscious familiarity, resembling source/destination routing on Google Maps, but gives the user a sense of progress towards a goal. Why? Psychology studies have shown that using a checklist inspires productivity. Similarly, we believe that the user's observation of a path shrinking as they walk will motivate them to reach the "check", resulting in faster deliveries and higher user satisfaction.
Familiarity
User Behavior
DESIGNING TO MOTIVATE
Deliverery and pickup points were projected to be within walking distance and it is easy to display both on the screen, so we provide a path on the map. This not only creates subconscious familiarity, resembling source/destination routing on Google Maps, but gives the user a sense of progress towards a goal.
​
Why? Psychology studies have shown that using a checklist inspires productivity. Similarly, the user's observation of a path shrinking as they walk will motivate them to reach the "check", resulting in faster deliveries and higher user satisfaction.
ITERATION #1 (HACKATHON EDITION)
We designed this interface to resemble existing crowdsourced delivery apps like Lyft and Uber, featuring a map. Deliverery and pickup points were projected to be within walking distance and it is easy to display both on the screen, so we provide a path on the map. This not only creates subconscious familiarity, resembling source/destination routing on Google Maps, but gives the user a sense of progress towards a goal.
Why? Psychology studies have shown that using a checklist inspires productivity. Similarly, we believe that the user's observation of a path shrinking as they walk will motivate them to reach the "check", resulting in faster deliveries and higher user satisfaction.
"Laziness Radius" is adjustable, and lets you find jobs close by.
Development of a number-less messaging system
FUTURE ITERATIONS
Considering that this app is about the orderer making "Quests" for their peers to complete, the black logo and overall design don't work to convey "adventure". It's also a leap of faith to trust a stranger to deliver your goods, even if they attend the same university as you. The design needs to somehow invoke trust.
​
The green logo gives off a much friendlier impression, using vibrant colors and sporting a boat shaped like a smile, a popular psychological trick used by many companies.
Brand Identity
Additional Features
1. Order tracking: allows orderers to see how close the deliverer is.
2. Gender Preference: i.e. women may only want deliveries from women. The judges and a few of our respondents asked about this feature.
3. Friends: keep track of deliverers/orderers with whom you've had good experiences, as well as friends who are also on the app. This creates a secure network of people you're comfortable asking for favors, leading to more app usage.
4. Micro-Transactions: when the service becomes large, we can no longer provide API calls for free, so we would need to use a service like Stripe to automatically take a cut of each transaction (rather than simply provide matching and allow people to pay through Venmo).