daypop

Role

User Interface Design

Tools

Sketch, Principle

Timeline

Nov - Dec 2016

daypop logo.png
 

problem

Busy lifestyles make it difficult to find and plan things to do with others as commitments in life grow. As a result, not only do people begin to fall out of touch with their community, but also with each other. Furthermore, so many event websites exist to sell tickets or advertisements for specific events requiring users to invest more time searching for an interesting event and planning around schedules with friends and family. For college students, exploring events on- and off-campus is a crucial factor of that helps them engage, experience, and influence the community around them.


our solution:

Our solution is a social scheduling mobile app that helps friends reconnect and discover events that matches their lifestyles. Events are aggregated from popular online sources and categorized to reduce the frustration involved with tracking events across many different websites, emails, and calendars. Developer access to 3rd party APIs from various sites would enable us to apply machine learning methods to deliver personalized event recommendations that adapt to a user’s interests, location, schedule, and friends’ activities. This would be released for major mobile platforms with development being sought through hybrid app environment such as Xamarin or a Java-based solution like React Native or Ionic. A framework like Django would allow us to easily facilitate backend operations including account management, content management, and user authentication. Azure would not only be used to host our backend system, but also leveraged to conduct predictive analytics and facilitate deployment to the user-facing mobile app.

Calendar Homepage.png
Nearby.png
Mockups.png

conSTRAINTS

  • Limited time and resources. 
  • We need a way to fulfill user needs while carefully considering any and all scheduling, interests, activities, locations, options. 
  • Keeping a natural flow between user needs and building a logical way to layer information and schedules. 
  • We've defined and identified our user, but the next question is: "does it make sense?" 
  • We need to take time to define peresonas and go through various iterations. This led to many sets of redos of wireframes and information architecture.