Home

Welcome to the hacking-the-browser wiki!

The class syllabus is here.

Create a “responsive” web page or codepen that responds to some unexpected aspect of the browsing experience. You can build on one of the demos we worked on in class (battery, geolocation, motion/orientation), or come up with something else. Possible examples are a page whose display changes based on battery level, or distance moved since opening the page, or proximity to some physical location, or when tilted totally on its side. Be ready to share your work. Since not all sites will be viewable live in class (if they involve time or location change, e.g.), include screenshots of your site in different scenarios.
Find an existing site to share. Something that pushes the boundaries of the web, in your opinion. We will look at a few of these in class.

Week 2

Make a bookmarklet that works against the user. It might make links harder to see/click (change color, move them around), remove form elements, put image/div on top of page, etc, make it less informative/useful. Interpret this how you like. It can be a bookmarklet that works generically on (most) sites, or one that is tailored for a specific site.
Find an interesting bookmarklet in the wild. Reverse-engineer it (see earlier slide about this) and be ready to explain how it works (as well as you can).

Homework

Turn last week’s bookmarklet into a Chrome Extension
Either:
- Improve #1 by using what we learned today to make it do something new
- Make an extension that helps the user somehow
Find an interesting extension in the wild and:
- look at its manifest.json to figure out how it works
- decide which category it is

Cory 1) link to your work in progress on your extension or a new extension that invades privacy or "has no purpose", 2) link to notes about reverse engineering an extension <--- Copy this line and paste it below, changing the info to match your own

The homework for week 5 is to prepare and polish your final projects and be ready to present them at our final class.

Your project should:

Presentation format:

8 minute presentation, 2 minute Q & A
I will use a timer and manage the clock (at 7 minutes the alarm will go off, letting you know to wrap up so you can take questions)
There will be 3 guest critics in class to see your work and provide feedback

Presentation details:

Use Slides
Include Images/Videos — code doesn't always work, especially in front of an audience. Use images and videos so you have a backup in case there's a technical issue with your code during your presentation
Show Code — be ready to walk through some of your code for the class, explaining how it works
Your project should work, but not necessarily perfectly
What did you learn?
What difficulties did you encounter along the way? How did you solve them or work around them?
Show research if applicable
What’s next? What's your vision for the project if you had more time to improve it?
In addition to talking about how your project works, also talk about what it means — to you, in the context of the browsing experience, etc.
Do a practice run-through of your presentation once before class so you have a sense for how long it is. If the presentation portion runs long there may not be time for you to answer questions.