Bikers and the rules of the road

Carrie and I have been talking a lot about traffic rules lately, and how we sometimes need to bend them to feel safer when biking in high traffic. Sometimes it feels so dangerous to take a left turn in a high-trafficked intersection, that we might ride a bit before the light turns green, because that’s the only time we can turn left without angry cars driving on all sides, and paralyzing us in the middle of the intersection. The Centre street / Reade street section right after the Brooklyn Bridge is one of those:

Tony Wessling a.k.a. The Upright Biker writes an interesting post about the subject of where the bikers fit into the traffic hierarchy, Bicyclists are not above the law – we’re below it. He states that the laws generally favor cars over bikers, even though we all pay for this infrastructure. When it comes to the red lights specifically, his philosophy is this:

Traffic lights, in addition to adding safety for motorists, cyclists, and pedestrians, are designed to regulate the flow of automobiles. The flow of bicycles does not really need much regulation at this point, so if there’s no danger, off I go. Once there are so many bikes on the road that their movement needs regulation, I’ll gladly stop. Did it in Amsterdam. Would do it in Copenhagen.
The Upright Biker

Bikers are different than cars, and we need to be very aware of that when designing our product. We can’t necessarily expect the biker to follow ALL rules at all times. We want our users to be safe on the bike, but sometimes safety and the rules of the road simply don’t match up.

Thesis Proposal

Elevator pitch:

It’s your bike’s better half. It knows you, your bike, and the city you live in. It offers you a seamless and enriched riding experience through giving you turn by turn directions, tracking your behavior, advising you on how to take care of your bike, and suggesting you destinations and routes that suit your taste.

Intended audience:
Intermediate riders
People currently biking in the city. They might already use navigational tools like bike maps and apps, and are searching for new ways to make their trips more seamless whether they want to get from A to B or wander.

Beginner riders
There’s a difference between knowing how to ride a bike, and being confident riding in an urban environment. Beginner riders might use their bike for recreational trips and are not yet convinced that biking can be a viable transit option.

Tourists on bikes
People that want to explore a new city from the bike seat. Might rent bikes from bike shops, or using bike share programs.

Context of project:
The bike community
Open Plans
Bike sharing program
Ride the City
Transportation Alternatives
New York City DOT
Bike Tech Meetup
Bike activists (bloggers, political figures, …)

Bike Tools
Biking apps that track behavior
Biking apps aiding navigation
Bike computers for pro cyclists
GPS for bikers (TOM TOM has turn by turn voice directions in Europe)

Products with related concepts
Motivational, data sharing, storytelling, creative personalities, way finding, trip planning, etc.
Websites and apps: Weight Watchers, RunKeeper, Nike+, Daytum, OpenTripPlanner, TripAdvisor, Yelp, Tamagotchi etc.

Intended Experience/Form:
Experience
A friendly and delightful product that is aware of what the biker needs and when.
It alleviates stress from biking in chaotic surroundings.
It inspires discovery of new places.
It eases the process of using your bike for transit.

Form
App + physical component (talking helmet, vibrating handlebars, blinking lights, …)

Plan & Next Steps:
Our overall goal is to create a working prototype that lets people experience the core concepts early on, and iterate the concept from there.

Our next steps (2 week perspective):

  • Create a journey map
    Zoom out and identify pain points and opportunities within the area of urban biking.
  • Create a conceptual model of project
    We narrow in on a concept suitable for our thesis.
  • Develop an MVP
    Software: Creating a web app for a user to input start and end point, and get directions through voice.
    Hardware: R&D for speakers, bluetooth, button, sensors, and connecting these pieces to each other and the app.
  • Do contextual research
    What’s out there? Dig deeper than the list above. Divide and conquer.

Alternative elevator pitch:

We’re making a digital bike companion to be used by urban peddlers to alleviate them of the stress of navigation in a heavy trafficked, stressful environment. Enabling people to experience the city seamlessly from the bike seat, offering directions, tracking, bike maintenance advice, and tips for urban destinations.

What if there were two buttons

We have a pretty good idea about what the minimum viable product (MVP) will do—ask where you are going, calculate a bike-safe route, give turn-by-turn directions and re-direct you when you’re lost. In the MVP itself, there are very big challenges. However, the trick is creating value beyond the basic product. Following are a few thoughts to get us started.

What if there were two buttons—I want to get lost or I don’t want to get lost. We should address the needs of the rider. And ask is it for exploration or transportation?

We can consider way-finding and how one moves from place to place. How can we build and ecosystem around biking as a mode of transportation? People move in the city based on going from one place to another. (For example, I’m at home and I’m going to my favorite pizza shop). They use tools like Yelp and Google Places to find where to go. They are also using apps like Foursquare and Gowalla to broadcast or track the places frequent. Can our application interact with these existing pieces of the ecosystem?

Sources for inspiration: Flight tracker and TripIt.

Follow-up notes from September 19, 2011 meeting with Frank Chimero at SVA

The Google Directions API

The Google Directions API is a service that calculates directions between locations using an HTTP request.

Note the following:

This service is generally designed for calculating directions for static (known in advance) addresses for placement of application content on a map; this service is not designed to respond in real time to user input, for example. For dynamic directions calculations (for example, within a user interface element), consult the documentation for the JavaScript API V3 Directions Service.

Still, by using the Google Directions API, you can get directions through putting URLs into the address bar on JSON or XML format. Here are som tests:

Home to Purpose:
http://maps.googleapis.com/maps/api/directions/json?origin=519+5th+st,+brooklyn,NY&destination=224+centre+st,NY&mode=bicycling&sensor=false

Home to Purpose – via Brooklyn bridge using waypoints:
http://maps.googleapis.com/maps/api/directions/json?origin=519+5th+st,+brooklyn,NY&destination=224+centre+st,NY&waypoints=brooklyn+bridge,NY&mode=bicycling&sensor=false
…though this breaks the route into two legs, and the directions says “destination will be on your left” also when I’m on Brooklyn Bridge…

Home to Purpose – alternative routes:
http://maps.googleapis.com/maps/api/directions/json?origin=519+5th+st,+brooklyn,NY&destination=224+centre+st,NY&alternatives=true&mode=bicycling&sensor=false

XML instead of json (json is recommended though):
http://maps.googleapis.com/maps/api/directions/xml?origin=519+5th+st,+brooklyn,NY&destination=224+centre+st,NY&mode=bicycling&sensor=false

This was the service I used when getting directions for the Low-fi prototyping, part II, which I then turned into a text file ready to be read by the guy from Speak It!

Some issues:

  • The directions do not seem to have information about bike path/lane in Google Maps. The Ride the City app does have this information.
  • For knowing the user’s current location, we might need to use the Official Google JavaScript API.

Low-fi prototyping, part II

After our last prototyping test suffered from bad sound quality from phone to phone, I figured it would be good to test audio coming from my own phone. I made a text file with directions to read. Then I let this charming British man in the app SpeakIt! read it out loud. Here’s the Speak it! audio file.

The file is one long file with text-to-speech directions read on this format:

1. Head southeast on 5th Street toward 8th Ave.
Ride about 282 feet.
Then turn left onto 8th Ave

2. Turn left onto 8th Ave
Ride about 0.1 miles.
Then turn left onto 2nd Street

3. Turn left onto 2nd Street
Ride about 0.4 miles.
Then turn right onto 5th Ave

4. Turn right onto 5th Ave
Ride about 0.6 miles.
Then turn left onto Bergen Street

5. Turn left onto Bergen Street
Ride about 0.5 miles.
Then turn right onto Bond Street

6. Turn right onto Bond Street
Ride about 253 feet.
Destination will be on the left
Address: 190 Dean Street

I tested it with Apple headphones (one plug in) and iPhone, using the remote on the headphones to pause after each bulk of directions. Of course I needed to know when to press play again myself, rather than getting it triggered by GPS knowing where I am. But other than that – VERY successful as the voice was loud and clear. Would definitely add info about which streets have bike path/lane to the instructions, though. I forgot about it when making the audio file.

Low-fi prototyping, part I

When considering doing a thesis together, it is very important to make sure that the thesis area we consider to commit to, is in fact an area that is thesis worthy. We both need to believe in the project, and we have to want to live with it for a long time. That is why we wanted to do a simple test of the concept of a bike companion giving in-ride directions out in the real world.

We prepared directions for each other, and planned to bike behind each other, giving directions at the appropriate time through a phone call. Equipment used:

  • Android phone with bluetooth headset
  • iPhone with apple ear buds

Bad sound quality was a big issue, and made it particularly hard to hear street names (which is the most important thing we figured). A phone call while biking gave us way too much wind noise and other interferences. Audio quality is KEY. We were talking about whether using bluetooth headphones rather than wired headphones would potentially not give us good enough audio. Need to check that.

We agreed on a good format for giving instructions. When next turn on 8th ave is approaching:

Turn left onto 8th avenue.
Ride about 0.1 miles.
Then turn left onto 2nd street.

When next turn on 2nd street is approaching:

Turn left onto 2nd street.
Ride about X miles.
Then turn right onto 5th avenue.

But adding whether there’s a bike lane/path would also be helpful, and maybe also on which side of the street the lane is on. In addition, we should consider ways to talk back or give other kind of feedback to the helmet. We might want to make it:

  • Repeat
  • Shut up

Other types of encouragement along the way were also discussed, and how to humanize the voice and the content. Important to figure out how to make the biking experience desirable/delightful. I.e. what happens when on a bridge etc.

These notes were taken on Cafe Martin in Park Slope after the bike ride. Then we rode our bikes to Brighton Beach, and discussed the possibility of thesis collaboration in the sunset.

Thesis Starting Point

I was riding my bike up Kent Avenue on my way from Carroll Gardens to Greenpoint. I had already taken three wrong turns when it hit me—I need helmet head. For those of you who aren’t familiar, helmet head was a concept for a talking bike companion that Kristin and I had developed with Allison Shaw and Tina Ye in last spring (2011) at SVA. In that moment, on Kent Ave, I desperately wanted it to exist.

We met at Gorilla cafe over steaming coffees.

“What do you think about building helmet head for thesis?” I asked Kristin. And the conversation began.

We want our thesis year to be about making something and putting it out in the world. Going beyond research and concepting to a darn good working prototype that we can hand to people to use is important to us. As a next step, we decided to talk with our former teammates, and do some experience testing and general tech research about how we could build the project. It’s going to be a pretty robust undertaking, so we should be sure before committing.

Our initial concept model for Helmet Head: