<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Leather Ducking &#187; Hardware</title>
	<atom:link href="http://leatherducking.com/category/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://leatherducking.com</link>
	<description>Thesis talk on urban biking by interaction designers Kristin Breivik and Carrie Stiens</description>
	<lastBuildDate>Mon, 07 May 2012 01:33:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Hardware Update</title>
		<link>http://leatherducking.com/hardware-update/</link>
		<comments>http://leatherducking.com/hardware-update/#comments</comments>
		<pubDate>Fri, 18 Nov 2011 22:14:36 +0000</pubDate>
		<dc:creator>Carrie Stiens</dc:creator>
				<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://leatherducking.com/?p=721</guid>
		<description><![CDATA[In the previous hardware post, I wrote about a few different directions we could go to integrate sensors with a mobile app. The simplest way, however, is to re-program a button on an existing bluetooth headset or wired earbuds. To &#8230; <a href="http://leatherducking.com/hardware-update/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>In the <a href="http://leatherducking.com/prototyping-options-for-features/">previous</a> hardware post, I wrote about a few different directions we could go to integrate sensors with a mobile app. The simplest way, however, is to re-program a button on an existing bluetooth headset or wired earbuds. To start, we can write a basic mobile app that will do &#8216;what we say&#8217; when the button is pressed. For example, with the &#8216;pin&#8217; feature, when the button is pressed the app will record the longitude, latitude and/or time.</p>
<p><a href="http://leatherducking.com/wp-content/uploads/2011/11/b-stock-sony-ericsson-wireless-stereo-headphones-hbh-is800.jpg"><img src="http://leatherducking.com/wp-content/uploads/2011/11/b-stock-sony-ericsson-wireless-stereo-headphones-hbh-is800-150x150.jpg" alt="" title="wireless-headphones" width="150" height="150" class="alignleft size-thumbnail wp-image-722" /></a></p>
<p>I found these <a href="http://www.amazon.com/Sony-Ericsson-Wireless-Stereo-Headphone/dp/B001QTW21Y/ref=sr_1_13?s=electronics&#038;ie=UTF8&#038;qid=1321654305&#038;sr=1-13">wireless headphones</a> the other day. While Apple&#8217;s wired earbuds will work just as well for initial experimenting, these could be a great wireless option. They both stream music and handle phone calls, as well as have the button input. </p>
]]></content:encoded>
			<wfw:commentRss>http://leatherducking.com/hardware-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Prototyping Features, Options</title>
		<link>http://leatherducking.com/prototyping-options-for-features/</link>
		<comments>http://leatherducking.com/prototyping-options-for-features/#comments</comments>
		<pubDate>Fri, 04 Nov 2011 19:56:00 +0000</pubDate>
		<dc:creator>Carrie Stiens</dc:creator>
				<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://leatherducking.com/?p=568</guid>
		<description><![CDATA[Note: We will probably need to purchase a smartphone for prototyping. I&#8217;m leaning much more toward the Android, not because I&#8217;m bias to my personal phone, but because as a platform it seems much more open for hacking than the &#8230; <a href="http://leatherducking.com/prototyping-options-for-features/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Note: We will probably need to purchase a smartphone for prototyping. I&#8217;m leaning much more toward the Android, not because I&#8217;m bias to my personal phone, but because as a platform it seems much more open for hacking than the iphone.</p>
<p><strong>PHYSICAL BUTTONS AND SENSORS FOR RIDER FEEDBACK</strong><br />
One option is to use a dev board to interface between the phone and extra components (button, force sensor, etc). This gives us room to play with various sensors that may be embedded into the helmet. Sparkfun has products that would help us with this. For example, here&#8217;s a <a href="http://www.sparkfun.com/products/10331">serial modem</a> that allows you to interface an Arduino board with the Android or iPhone through the audio jack. This car audio <a href="http://www.wisebread.com/build-a-cable-to-control-your-android-phone-while-you-drive" title="project">project</a>, also connecting with the phone through the audio jack, demonstrates the beauty of a physical button paired with a mobile phone.</p>
<p>Note: Wires are required for the first two examples. I think this is okay for early prototypes, but in the end, we do want to be wireless.</p>
<p>An alternative route is to hack the existing button on a bluetooth headset (or audio headphones) and reprogram it to do different commands. There are several examples of people doing this type of hack to boost the volume of audio, and perhaps there would be some direct correlations for what we would need to do. This gives us less control over selecting physical components, but may be more simple.</p>
<p><strong>WHAT TO DO WHEN THE BUTTON WORKS</strong><br />
There are a couple simple things the button could to in the beginning to test the feasibility and experience of considered features:<br />
1. To pin places; &#8220;Remember this location (longitude and latitude)&#8221;<br />
2. To start/stop tracking</p>
<p><strong>AND FINALLY FOR TRACKING AND GEO-LOCATION SOFTWARE</strong><br />
To be determined&#8230;We need something simple and with an open API. </p>
<p><strong>STARTING POINTS FOR ANDROID APP DEVELOPMENT</strong><br />
A <a href="http://www.youtube.com/watch?v=I6ObTqIiYfE">first look</a> at building and android app<br />
Android development <a href="http://www.vogella.de/articles/Android/article.html">tutorial</a><br />
A bit about the <a href="http://www.vogella.de/articles/AndroidLocationAPI/article.html#overview_locationapi">android location API</a><br />
Another <a href="http://hackaday.com/2010/07/12/android-development-101-%E2%80%93-a-tutorial-series/">android development 101</a></p>
]]></content:encoded>
			<wfw:commentRss>http://leatherducking.com/prototyping-options-for-features/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Hardware Sketch</title>
		<link>http://leatherducking.com/hardwaresketch/</link>
		<comments>http://leatherducking.com/hardwaresketch/#comments</comments>
		<pubDate>Sun, 02 Oct 2011 00:15:02 +0000</pubDate>
		<dc:creator>Carrie Stiens</dc:creator>
				<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://leatherducking.com/?p=201</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p><a href="http://leatherducking.com/wp-content/uploads/2011/10/helmet_diagram4.png"><img src="http://leatherducking.com/wp-content/uploads/2011/10/helmet_diagram4.png" alt="" title="helmet_diagram" width="524" height="284" class="aligncenter size-full wp-image-256" style="border:none;"></a></p>
]]></content:encoded>
			<wfw:commentRss>http://leatherducking.com/hardwaresketch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
