First front-end development product

Coding in the wild… a test

For my first project, I plan to design a site that will do the following:

NYC Recycling Schedules and Exceptions

  1. user enters address
  2. site reports back the recycling schedule for that address on the day in question
  3. options include:
    • regular scheduled delivery, in which case icons will appear showing the items to be put out for recycling.
    • no delivery scheduled
    • delivery exception, which might then trigger email to signed up users

To access this information, I have New York’s 311 API. I will also need to work out email address sending, which also means an email signup form. Ideally the email can be automatically generated, perhaps listing the reason for the exception. This also means that when the user signs up to use the site, I will need to save their email address and street address. Without being creepy. Ultimately it would be cool to open it up to GoogleNow, so reminders and exceptions could appear in the GoogleNow cards without a user having to check email. Pipe dreams. For now it will be powered by HTML5, CSS and JavaScript.

This idea came to me as our building was handed yet another sanitation fine, seemingly at random by the Department of Sanitation. Each fine is $ 100, and it’s starting to add up. I’m pretty good on the regularly-scheduled pick-ups but the exceptions, due to holiday schedules or inclement weather cause problems because then the rubbish is just left to pile up. This in itself usually doesn’t result in a fine, but it does mean the rubbish gets ripped open, causing it to spill on the street, and that does result in a fine. No more! No more! It’s quite cool that this is going to happen, I can tick something off my project list, as referenced in this earlier post.

One thought on “First front-end development product”

Leave a Reply

Your email address will not be published. Required fields are marked *