Home - comp346s17/course-project-zombie-zapper GitHub Wiki

Welcome to the ZombieZapper wiki!

Team Name: Computer Bagel Boys

Team Members: Austin K, David M, Micah T

Project Title: Zombie Zapper

**Description: **

We all have habits that dictate our daily lives. Some people are able to take control of their recurring patterns of behavior, but for many of us, breaking our unwanted habits and beginning desired habits is a difficult endeavour. This app will help those people who need assistance starting and stopping habits by crowd-sourcing solutions and identifying problems for habit forming/breaking. The website will have categories of behavior and under these categories there will exist sub-behaviors that are used to achieve the larger behavior. Users will be able to create both the larger behaviors and sub-behaviors, and they will be able to search for the behavior categories that they are interested in. The users will subscribe to behaviors that will help them achieve their larger goal. Users will have the option to receive emails to remind them about behaviors that they are trying to start/stop. The emails will have contain a yes/no clickable button that helps track their progress with their desired behavior. Users who do not wish to receive emails will be prompted to complete a small survey to track their progress. User progress will be tracked using a level system that is associated with the number of positive behavior changes they have successfully made. The user’s level can only go up and only their successes will determine their level. Even if a user fails most of the time, their successes will slowly accumulate and their level will increase. 

This application will have dynamic content and data residing in a database that will need to be queried to display. The design will need to be neat and engaging so that people will not feel overwhelmed when they are interacting with the application; it will be overwhelming enough for them attempt to start or stop new behaviors. Because much of the content will be crowd-sourced, displaying the information that resides on the site will be challenging and will require the use of AJAX and dynamic, interactive content.

Team Roles and Responsibilities:

David: Will work on back end design: database management and model

Austin: Implementing interface: logic and interactive elements Project manager, making sure we are following timeline

Micah: Design mockups and user interface ideas

Timeline:

We will be following the schedule on the course project informational sheet and meeting after each class to discuss progress and goals so that we are able to turn everything in on time. Development and Milestones Plan

  • 3/30: Propose 2-3 preliminary wireframes and basic design mockups so that we can explore what designs will be meaningful. Look at similar and unique user-content crowd-sourcing sites to see how they display information and input from crowds of users (IE Reddit, Kickstarter, Quora, Twitch, etc)
  • 4/4: Select favorite wireframe as well as any useful implementations of crowd-sourced display categories. Begin doing basic software architecture as well as implementation of data models and UIs. Create basic home page implementation wireframe.
  • 4/6: Research different UI tools as well as pick a basic color scheme. Begin looking into design of logo (if possible). Create wireframes of User login page as well as basic forum page. Look into alternatives for dynamic UI elements such as user input. According to data model, what other sites do we need?
  • 4/15: Finalize logo and begin creating UI for necessary pages
  • 4/18: Finish designs of all pages including: color scheme, logo, basic pages
  • 4/19: If not already done, create sample database for required data for each page.
  • 4/20: Review our data model. If not on track of what is necessary, redraft a better one.
  • 4/23: Determine how GET and POST requests should work. Depending on our site architecture, if we want something like Twitch, socket knowledge may also be necessary
  • 4/25: Connect Server and Front-end together using JS
  • 4/30: At this point, User creation, User posts and other basic capabilities will be in place. If there is time, work on adding other functions such as texting/emailing, notification system, User deletion, moderators, etc. The idea of something like Reddit’s ‘gold’ could also be really fun.
  • 5/2: Write Readme. Create slides and talk about our inspiration (BJ Fogg)
  • 5/3: Practice Presentation and Demo

Support We all have varying levels of experience in front-end development, but not a lot of experience in back-end. We expect running a crowd-sourcing web application would come with its own set of unique challenges, so help in constructing a viable data model once we’ve clarified finer details of form and function would be appreciated.