https://github.com/saulshanabrook/cell-plans

Comparing US Cell Phone Plans
https://github.com/saulshanabrook/cell-plans

Last synced: 7 days ago
JSON representation

Comparing US Cell Phone Plans

• Host: GitHub
• URL: https://github.com/saulshanabrook/cell-plans
• Owner: saulshanabrook
• Created: 2013-09-22T20:32:53.000Z (about 11 years ago)
• Default Branch: master
• Last Pushed: 2013-09-23T02:36:47.000Z (about 11 years ago)
• Last Synced: 2023-03-23T11:43:56.028Z (over 1 year ago)
• Size: 125 KB
• Stars: 1
• Watchers: 0
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

README

        

# Background

having a cell phone plan is expensive. not only is it expensive, but

it is hard to find what plan offers the best deal considering your

needs. So why not make a web app to compare phone plans?

# Design

We need to be able to specify what we need and then see a comparison

of the different plans, so we can effectively look at the cost vs.

the quality of each option.

## Specifying our needs

There are a number of requirements we might have when looking for a cell

plan. We should support the most common first.

1. multiple devices. Each device should have:

   1. Domestic usage

      1. number of minutes

      2. number of texts

      3. amount of data

   2. type of phone

      1. basic vs smartphone

      2. type of smartphone

2. carrier

## Listing the competition

Once a user has specified what they want, we should list the possible

options, sorted by price.

# Implementation

since this is useful to the general public it should be a website.

it does need to by the end user, and really could be a single page

web app, completely static. that means that representation and data

storage must all be done with javascript.

## Framework

I want to use [polymer](http://www.polymer-project.org/) as the

javascript framework, because it seems like it will be the future. From

their [FAQ](http://www.polymer-project.org/faq.html#why)

> Unlike some other frameworks before it, Polymer attempts to embrace

  HTML as much as possible by encouraging the use of custom element

  wherever possible. It includes a handful of independent polyfills

  for these emerging web standards (Custom Elements, Shadow DOM, etc.)

  that over time, diminish and ultimately disappear as browser vendors

  implement the native APIs.

To get a sense of what polymer is I recommend watching the [Google IO

video on Web Components](http://www.youtube.com/watch?v=fqULJBBEVQE)

and then the one on [Polymer](https://www.youtube.com/watch?v=0g0oOOT86NY)

# Contributing

this a project for the community., so please lend your voice.

there are some guidelines for contribution

1. all development must be done in separate branches, and then merged

   into master

2. follow appropriate code standards