A New Way to Pass-StudyBuddy

The Team:

  • Alexander Hagan (ahagan@princeton.edu)
  • Malika Oak (moak@princeton.edu)
  • Ajay Penmatcha (ajayp@princeton.edu)
  • Carl Sun (carlsun@princeton.edu)
  • Kevin Tsao (ktsao@princeton.edu)

Brief Overview:

Study Buddy is a mobile application, hopefully available on both the iOS and Android platform, that intends to make the process of group studying easier for University students. It provides an interactive map interface that displays information regarding currently active study groups in the subjects and courses of the user’s interest. The goal of the application is to bring together students who don’t have pre-made study groups and want the same.

Current Timeline for Project:

  • 3/11 – 3/17:

    • Finish Design Document
    • Finish initial planning
  • 3/18 – 3/24:

    • Learn REACT
    • Familiarize with language and tools being used
    • Set up Github and the Server/database
  • 3/25 – 3/31:

    • Finish home page design and code
    • Finish group choice page design and code
  • 4/1 – 4/7:

    • Finish “In a Group” page design and code
    • Make sure pages all link to each other properly
  • 4/8 – 4/14:

    • Make sure first iteration is fully functional for prototyping​; Must be able to​:
      • Allow registering with Princeton email
      • Allow group creation for any Princeton course
      • Allow time management and passing of authority for said groups
      • Allow searching for current groups in a class
      • Allow joining of existing groups
      • Allow ending of a group early
      • Allow settings tab for adding/removing *interesting* courses (those that they want to follow or are in, for example)
      • Allow users to indicate interest without forming a group
      • If notifications are on, get push notification for group being created in a certain class
  • 4/15 – 4/21:

    • Add extra features we want that are not as essential for Alpha test, including:
      • The temporary “forum” for group discussion and sharing
      • Customizable color palette
      • CAS implementation
      • Suggestions we receive from users
  • 4/22 – 4/28:

    • Continue and finish Alpha test (be done by 4/27)
  • 4/29 – 5/5:

    • Finish Beta test, adding any extra features and fixing anything wrong (be done by 5/3)
  • 5/6 – 5/12:

    • Prepare for demo day
    • Add any finishing suggestions by 5/13