Feedbaker is an online audience response system.
JavaScript CSS
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Table of Contents

  1. Overview
  2. Ideation
  3. Goals for Milestones
  4. References Used
  5. Project Logbook

1. Overview

Feedbaker is an online audience response system.

Our project introduces an easy and convenient way for presenters to get instance feedback from their audience. Professors, teaching assistants or students can use Feedbaker during lessons and presentations to gather responses from their audience for purposes such as to assess the general understanding of the audience, or to conduct a live quiz.

Traditionally, this would require expensive infrastructure and hardware. Feedbaker effectively eliminates the need for a audience response device which is costly to acquire. Instead, the audience can use devices that they already own (such as their smartphone or laptops) to respond to questions set out by the presenter.

We hope that our project (in its simplicity) is able to address some of the abovementioned concerns and provide an alternate way for people to do surveys and polls. This platform is currently set to authenticate with NUS OpenID, but can easily be extended to authenticate with other OpenID providers.

Our target level of achievement: Level II: Gemini.

2. Ideation

User Stories:

  • As a presenter, I want to be able to conduct live polls during my presentation to have increased interaction with my audience.
  • As a presenter, I want to be able to get realtime feedback to make my presentations interesting and to facilitate fluid discussions.
  • As a user, I want to be able to create a simple votable question so as to make decisions based on popularity. (many possible uses for decision making)
  • As a user, I want to keep track of the polls I've conducted so that I can remember what the results were.
  • As a student, I want to forget about the hassle of keeping a 100 dollar responder device for my surveys in class.
  • As a teaching staff, I want to get simple feedback quickly and as painlessly as possible without resorting to IVLE quizzes and forums.

Distilling from these user stories, we have identified a few core features that the polling system would need to have:

  • Multiple choice questions and answers
  • Live charts results display
  • Real-time results feedback
  • Poll management system

Extensions to this project may include:

  • Open project out to anyone to use
  • Choice of Data Visualisation (Pie, Line, etc)
  • "Youtube Live Comments" concept of open-ended results (comments)

A complete description and outline of our plans and decisions have been consolidated in a table which you may view here.

3. Goals for Milestones

A planned timeline of our project roadmap can be found here.

4. References Used

For this project, we depend heavily on the use of documentation on the following technologies (this list can also be found here):

Component Technology
OS Ubuntu
Platform NodeJS
Server ExpressJS
Server (Reverse Proxy) Nginx
Database MongoDB
JavaScript MVW Framework AngularJS
Front-end UI Framework Bootstrap
Authentication NUS OpenID
Version Control Github
Project Blog orbital.jon.sg

A complete list of the JavaScript packages and libraries which we have used in this project can be found in the following files in our Git repository:

5. Project Logbook

For all purposes and documentation of the lessons learnt and discoveries in this project, we have kept a journal that you may browse at our:

Project Blog: Feedbaker - NUS Orbital Project A summary of the number of hours as well as a full description and the substantiation to our progress and learning experiences have been meticulously compiled and presented for sharing in the following spreadsheet:

Google Spreadsheet: [NUS Orbital 2014] Team Jonathans: Project Log

As of the first Milestone, the total number of hours logged for both members:

As of the second Milestone, the total number of hours logged for both members:

As of the third Milestone, the total number of hours logged for both members:

Team total hours: 351 hours