7. Wireframes and Titles

First I'll start off with this interesting video of a contact-less dynamo light. I think technology like this would be perfect for the bike mounted beacons.




After producing 3 scenarios worth of drawn wireframes, the system seems to be taking shape. Morals are up to say the least.

Before I started sketching, I did review the previously proposed scenarios, back when I was considering  the personas. It seemed some condensing could be done, and there wasn't a previous scenario from the perspective of a Department of Transportation worker using the system. This sparked some interesting dialogue in the group critique from my peers and professor as well. So a new question has come to mind, not so much a new design question, but one that must be considered when moving forward with the new scenarios.

"In the communication and interaction between Kansas City cyclists and the Department of Transportation, where is the line of power drawn?"

It shouldn't be a negotiation on the part of the cyclists. So previously, as seen in the 3rd scenario proposed at the group critique, the DoT users have been in a sort of moderator position in the system. They acted as a special user with a different interface to post responses to safety issues that are uploaded by the cyclists. But this system seems really round a bout, and could be streamlined my simply minimizing the interaction between cyclists and DoT users.

So moving forward, I'll be looking at shortening 3 scenarios into 2. This will give me more time for design decisions and visual identity and navigation of the system. It should also create more engaging and dense scenarios for the viewers of my presentation.

Scenario #1: User tracks his route, uploads a safety hazard, and views a proposal for a lane on that road.

• User starts the app, immediately tracks route without having to enter the application   fully. 
• Rides his route.
• Turns off the tracking, and views his route he just rode visualized on a map.
• Is prompted to post any safety issues he encountered on the way. He did and does.
• Types the safety issue in the form of a sort of comment. Posts it.
• Other cyclists can now view this safety issue in the street viewer.
• The safety issue is shown as an icon on the route where he placed it, but it has a notification over it, or urges him to enter the safety icon.
• He enters it and sees that the safety count for that road has been reached with his newest safety hazard, and it is automatically scheduled for bike lanes to be installed. The page shows the estimated time till completion, and it's current construction status.
• The previous icon changes from a traffic cone to a bike lane icon, so the bike community knows that lanes are being put there.

Scenario #2: User receives a recommended route, rates it, and saves it.

• User enters the route section of the application, showing all of his routes previously travelled. He touches one to focus on riding, and the application zooms in to that route.
• When he taps the route to start his ride, a notification pops up with the traffic cone icon (signifying a safety notification). It says there is a route that is safer for him to take, and has been recommended by other users that rated the route fairly high. He touches the "try it" option.
• He rides the route.
• At the end of the route, it asks if there were any safety issues. He says no, and is presented with the options to rate and save the route.
• He rates and saves the route, and is taken to his routes page again, updated with the new route. The old one is still there if he still wants to ride it at another time.
• He then navigates to the city/ map section of the application. 
• He touches the view tab at the side of the screen and it expands with viewing options.
• He chooses the safety option, and the tab hides the options again. The map shows any safety issues posted by other users around him.
• He touches the video icon, which activates his camera.
• Using augmented reality,  he can see the safety icons in the environment, exactly where they were plotted by other cyclists.
• He touches one after looking around him, and it expands to show the comment as posted. It also shows the safety rating of that street. 

Moving forward, I'm also considering a few titles for the system. Some contain double meanings, and I'm most interested in those with a cyclist meaning, and a meaning pertaining to the system:

1. Portage: Portage is a term used by cyclists to refer to the carrying of their bicycle over their shoulder. It's a common occurrence in the city, and is used widely in bike commuting from place to place. It is a term unifying bike and cyclist, and represents perseverance. 
2. Tread: Is one of my favorite choices thus far. It refers to the rubber pattern or texture over the surface of a bike tire, as well as the mark it can leave behind in the bikes wake. So in this way, it shows where the biker has been; a route. So there is some interesting language that could be carried into the tracking application.
3. Cog: A cog is a gear responsible for propelling the bike forward when the pedals are moved. It's the center of motion for the bike. So cog could refer to the application as the center for bike movement around the city.
4. Route: Simple enough, but doesn't really have extra meanings.
5. The Hub: My second favorite of the options. A hub is the center of a bike wheel, but also has roots in design as the center of an online system that links together multiple platforms or elements. 
6. Brain: Brain is a cyclist term for a bike mounted computer, like a gps unit.