<?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>The Beast Within &#187; iphone</title>
	<atom:link href="http://beastwith.in/tag/iphone/feed/" rel="self" type="application/rss+xml" />
	<link>http://beastwith.in</link>
	<description>A mental brouhaha, est. 1996.</description>
	<lastBuildDate>Wed, 23 May 2012 23:49:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Is the Pebble smartwatch worth it?</title>
		<link>http://beastwith.in/2012/05/08/pebble-smartwatch-worth-it/</link>
		<comments>http://beastwith.in/2012/05/08/pebble-smartwatch-worth-it/#comments</comments>
		<pubDate>Tue, 08 May 2012 17:23:29 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[accessories]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[gadget]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[pebble]]></category>
		<category><![CDATA[watch]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2917</guid>
		<description><![CDATA[The idea of a smartwatch appears to have the same level of appeal to those of Generation X as the jetpack does. Both devices come from science fiction, and while technology has touched upon both, neither device has really entered consumer reality yet, though both have often been promised. The Pebble e-paper watch comes closest [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="T" class="cap"><span>T</span></span>he idea of a <em>smartwatch</em> appears to have the same level of appeal to those of Generation X as the jetpack does. Both devices come from science fiction, and while technology has touched upon both, neither device has really entered consumer reality yet, though both have often been promised.</p>

<p><a href="http://www.kickstarter.com/projects/597507018/pebble-e-paper-watch-for-iphone-and-android">The Pebble</a> e-paper watch comes closest to realizing the smartwatch as we&#8217;ve yet seen. If you haven&#8217;t already heard of the Pebble, it&#8217;s a Kickstarter project whose funding has already surpassed eight million dollars, so it&#8217;s pretty clear the project is popular, and is currently Kickstarter&#8217;s most-funded project ever.</p>

<h3>The good.</h3>

<p>The Pebble is designed to work with iOS and Android devices, using Bluetooth to speak with a smartphone. Chiefly, the Pebble aims to serve as a remote notification center, so you don&#8217;t need to look at your phone whenever a notification comes in. The Pebble provides notification for the following:</p>

<blockquote>
  <ul>
  <li>Incoming Caller ID</li>
  <li>Email (Gmail or any IMAP email account)</li>
  <li>Calendar Alerts</li>
  <li>Facebook Messages</li>
  <li>Twitter</li>
  <li>Weather Alerts</li>
  <li>Silent vibrating alarm and timer</li>
  </ul>
</blockquote>

<p>The Pebble also touts interoperability with certain smartphone apps, so it can control your smartphone&#8217;s music, access GPS data for cycling/running, etc. Out-of-box, the Pebble will presumably work with a couple key apps, but will primarily serve as a notification center until you grab third-party apps from the Pebble online store.</p>

<h3>The bad.</h3>

<p>Your notifications sent to your watch may be cool, but we see this as more of a novelty than a truly useful feature; the Pebble simply doesn&#8217;t offer any features that a smartphone by itself <em>doesn&#8217;t</em>. Yes, it puts notifications on your wrist, but for how many niche cases is that truly an improvement over just looking at your phone? Given the short range of Bluetooth, you have to have your phone near the Pebble anyway, so is saving you from pulling your phone from your pocket really worth $115? If a notification is important enough to respond to, you&#8217;ll have to pull your phone out anyway. If you&#8217;re not expecting an important notification, you can probably go without checking your wrist until you&#8217;re in a place you can use your phone.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup></p>

<p>It&#8217;s not that we <em>can&#8217;t</em> think of ways to use the Pebble, it&#8217;s simply that we&#8217;re not convinced the Pebble is going to make anyone&#8217;s mobile computing life <em>better</em>. Sure, that&#8217;s subjective, but in terms of efficiency, all the Pebble is doing is adding another layer of technology between you and your smartphone, and when is that a good thing? Again, outside of extremely specific use cases, the Pebble is a great novelty item, but little more.</p>

<h3>The ugly.</h3>

<p>Outside of the Pebble being a neat gadget, there&#8217;s the form factor to consider. Some people wear the iPod Nano as a watch because they love the digital watch-faces but the Nano is a really big watch. For those with smaller wrists, the Nano just looks silly, and the Pebble is similarly big. Pebble&#8217;s main Kickstarter page doesn&#8217;t include dimensions,<sup id="fnref:2"><a href="#fn:2" rel="footnote">2</a></sup> but <a href="http://forums.getpebble.com/topics/198">looking into it further</a>, we found that the Pebble&#8217;s body is roughly 5cm x 3cm. Compare this to the iPod Nano&#8217;s 3.75cm x 4.09cm dimension body, and you can see that the Pebble is no small beast. We wonder how many backers didn&#8217;t even consider this when pledging.</p>

<p>The size is also a concern because it means the Pebble pretty much needs to replace a watch. Whereas other wrist gadgets can sit alongside a watch, the Pebble really can&#8217;t, and wearing it on the wrist opposite your watch just looks like you&#8217;re wearing two watches. That may not be a concern for everyone, but we wonder how more versatile the Pebble would be if it had a thinner display that wrapped around more of the wrist, and scrolled notifications accordingly.</p>

<p>Another design concern we have is the plastic screen (as opposed to the crystal many watches sport), as plastic scratches much easier than glass. Yet, the biggest problem with the Pebble is that it&#8217;s limited to existing APIs, as well as the hardware it <em>doesn&#8217;t</em> have. There&#8217;s no line-out for plugging headphones in, for example, so you can&#8217;t entirely stash your phone for when you plan to take the Pebble on a run.<sup id="fnref:3"><a href="#fn:3" rel="footnote">3</a></sup> In many cases, you&#8217;ll still be using an armband to exercise with the iPhone, because the Pebble doesn&#8217;t offer a way around this.</p>

<p>On the iPhone, the Pebble also can&#8217;t read text messages, which limits what it can do with notifications.</p>

<h3>Hope is in the SDK.</h3>

<p>While the core functionality of the Pebble puts a purchase to question, the device&#8217;s saving grace may very well be its intended third-party support. The Pebble will have an SDK available before release, so third-party developers could have iPhone apps working with the Pebble as soon as the watch is released. The most high-profile iPhone app to have announced Pebble support thus far is RunKeeper, so we wouldn&#8217;t be surprised to see others take the plunge. A companion app for Zombies, Run!, for example, would be quite cool.</p>

<p>One area we&#8217;re looking forward to is activity-monitoring. The Pebble includes a gyroscope and vibration motor, so it has all the hardware necessary to compete against the Jawbone UP and Nike FuelBand. While no activity-and-sleep-monitoring apps have yet been announced for the Pebble, the potential is there, and we hope to see someone tackle this. At present, the Jawbone UP is the only wrist-wearable gadget that does full-on sleep and motion tracking, and there are still concerns over Jawbone&#8217;s quality control with the UP. As the Nike  Fuelband doesn&#8217;t track sleep or provide activity alarms, the market is ripe for the Pebble to fill this void.</p>

<h3>Our recommendation?</h3>

<p>We see buying a Pebble as an investment in <em>potential</em> functionality. Today, the developers announced a production cap of 75,000 Pebble watches for the initial Kickstarter drive, so there are roughly 10,000 watches left for reserve. We decided to back the project, figuring the worst case scenario is that we don&#8217;t see an activity/sleep-moniting app in the Pebble&#8217;s future, or the watch is simply too big for our wrists, and we sell the watch online. Given the demand for it, backers shouldn&#8217;t have a problem reselling their wares if they need to, and may even be able to make a couple dollars on it; if you&#8217;re on the fence, you probably won&#8217;t <em>lose</em> money on the Pebble.</p>

<p>Best case scenario for us is a proper activity/sleep-monitor app being released shortly after the Pebble store goes live. In this case, our worst decision will be deciding to forego a nice watch and instead wear the Pebble nearly full-time.</p>

<p>At the very least, the Pebble is a cool experiment in whether this market is capable of flourishing, let alone existing. There&#8217;s also the potential we&#8217;ll see a really killer app for the Pebble that no one&#8217;s thought of yet, so lurking Pebble&#8217;s developer forum should prove interesting in the days ahead. The Pebble&#8217;s estimated ship date is September, so there&#8217;s plenty of time for new app ideas to be thrown around and worked on. So while the Pebble&#8217;s basic functions don&#8217;t excite us, we&#8217;re looking forward to what developers come up with in the days ahead.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2011/09/27/our-iphone-4/" rel="bookmark" title="September 27, 2011">On our iPhone 4.</a> &#8211; The iPhone 4 is indeed a great phone, and [Shawn Blanc summarizes](http://feedproxy.google.com/~r/sh&#8230;</li>

<li><a href="http://beastwith.in/2007/07/11/the-iphone-is-cheap/" rel="bookmark" title="July 11, 2007">The iPhone is cheap?</a> &#8211; Since getting his hands on an iPhone, Michael of Apple Gazette has been running a column entitled &#8220;3&#8230;</li>

<li><a href="http://beastwith.in/2012/04/29/nike-fuelband-jawbone-up/" rel="bookmark" title="April 29, 2012">The Nike+ Fuelband takes on the Jawbone UP.</a> &#8211; After receiving our fifth Jawbone UP, we decided to seriously look into the newest competitor in the&#8230;</li>
</ul>

<!-- Similar Posts took 16.765 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>And in what situation is this even plausible? A formal business meeting where you don&#8217;t want to be caught looking at your phone, yet where looking at your smartwatch is somehow more acceptable?&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:2">
<p>It&#8217;s a bit telling that the Pebble&#8217;s watch-related specs are missing from the page; it paints a picture that the Pebble is a remote notification center first, and a watch second.&#160;<a href="#fnref:2" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:3">
<p>Unless you don&#8217;t care about listening to music while running, of course.&#160;<a href="#fnref:3" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/05/08/pebble-smartwatch-worth-it/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Jawbone UP replacement bands are duds.</title>
		<link>http://beastwith.in/2012/05/07/jawbone-up-replacement-bands-duds/</link>
		<comments>http://beastwith.in/2012/05/07/jawbone-up-replacement-bands-duds/#comments</comments>
		<pubDate>Mon, 07 May 2012 17:08:56 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[accessories]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[jawbone]]></category>
		<category><![CDATA[up]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2916</guid>
		<description><![CDATA[After weeks of use, our fourth Jawbone UP replacement band, and fifth UP overall, has finally died. We only reported on the death of our last UP band a little over a month ago, so the trend of late seems to be about one month of life per band. Battery life on our fifth band [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="A" class="cap"><span>A</span></span>fter weeks of use, our fourth Jawbone UP replacement band, and fifth UP overall, has finally died. We only reported on the death of <a href="http://beastwith.in/2012/03/29/fourth-jawbone-up-dead/">our last UP band</a> a little over a month ago, so the trend of late seems to be about one month of life per band.</p>

<p>Battery life on our fifth band seemed reasonable, with no real indication anything bad was about to happen. It was a week at least since our last full charge, and when the band was at around 10%, we forgot to top it off and instead let the battery expire. At this point, we plugged the band into a power source, waited until the LED went from red to white, and tried to sync the UP with our iPhone. It wouldn&#8217;t.</p>

<p>We tried both a soft reset as well as a hard reset. Rebooting our iPhone, per the instructions at the UP support site, didn&#8217;t help either. Instead of writing in about our problem as we had in the past, instead we called Jawbone yesterday, and were greeted by a very cheerful support representative. She suggested we plug the UP into our iPhone after we launched the voice memos app, as an UP capable of syncing should move the volume needle because it&#8217;s transmitting data using audio. We tried this, yet the needle didn&#8217;t move. That confirmed our UP was toast.</p>

<p>A sixth band should be on its way soon. As we had a support representative on the phone already, we took the opportunity to ask about the status of a <em>revised</em> UP without these problems. We had wondered several times before whether the bands Jawbone was sending out as replacements were known to have problems, or if this was effectively an ongoing &#8220;beta&#8221; period where Jawbone was <em>trying</em> to it right by sending out bands with small changes. The support representative confirmed that the <em>former</em> was true: Jawbone&#8217;s replacement bands are all <em>original</em> bands with known problems, and in all likelihood, would also fail.</p>

<p>Basically, replacing dead bands with those prone to failure is a stop-gap measure. Eventually, Jawbone will &#8220;relaunch&#8221; the UP in a revised, working state. But the representative didn&#8217;t know <em>when</em> that relaunch would happen. In short, if the relaunch happens before November, and we have a dead band at that time, we can request a <em>proper</em> replacement. In the meantime, we either keep trading dead bands in about once-per-month, or give up until the relaunch.</p>

<p>The representative reminded us of Jawbone&#8217;s no-questions-asked-refund policy regarding the UP, which we&#8217;ve already taken advantage of. At this point, having received a refund for the UP, we&#8217;re basically paying to use the UP with whatever time we spend dealing with the replacement process once per month. Considering we <em>do</em> like the functionality of the UP, and haven&#8217;t found a suitable alternative, we&#8217;ll continue playing this replacement game for the forseeable future, hoping that the relaunch will put an end to this cycle soon.</p>

<p>It&#8217;s a frustrating experience, but we have no doubt that Jawbone is legitimately embarassed by their lack of testing before the UP was sold last year. That&#8217;s why they continue to replace these bands at what must be considerable cost, particularly when they&#8217;ve already refunded many of the original purchases. Jawbone could have simply provided refunds and <em>not</em> continued sending replacement bands to the respective customers, but they&#8217;ve instead taken the high road.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup> If they can manage to relaunch the UP within the warranty period, they&#8217;ll manage to keep many of their customers, but if they <em>don&#8217;t</em> relaunch in time, we expect considerable outcry from their users.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2012/03/29/fourth-jawbone-up-dead/" rel="bookmark" title="March 29, 2012">Our fourth Jawbone up, dead.</a> &#8211; When we last reported on our experience with the Jawbone UP, we had just received our third band, ho&#8230;</li>

<li><a href="http://beastwith.in/2012/02/29/jawbone-up-trilogy/" rel="bookmark" title="February 29, 2012">Our Jawbone UP trilogy.</a> &#8211; Two months ago, we reported on the death of our Jawbone UP. It lasted longer than other folks&#8217; units&#8230;</li>

<li><a href="http://beastwith.in/2011/12/30/heres-to-jawbones-customer-service/" rel="bookmark" title="December 30, 2011">Here&#8217;s to Jawbone&#8217;s customer service.</a> &#8211; As a followup to our last post on the Jawbone UP, we thought it appropriate to provide an update to &#8230;</li>
</ul>

<!-- Similar Posts took 8.618 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>What irks us most about this replacement business is that Jawbone wasn&#8217;t very open in the past about replacement bands being prone to the same problems. We would have prefered Jawbone make this clear from the get-go, telling customers that they&#8217;ll keep replacing the bands with the understanding that the replacements are <em>not</em> expected to last much longer than the original band.&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/05/07/jawbone-up-replacement-bands-duds/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Nike+ Fuelband takes on the Jawbone UP.</title>
		<link>http://beastwith.in/2012/04/29/nike-fuelband-jawbone-up/</link>
		<comments>http://beastwith.in/2012/04/29/nike-fuelband-jawbone-up/#comments</comments>
		<pubDate>Sun, 29 Apr 2012 08:56:24 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[accessories]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[jawbone]]></category>
		<category><![CDATA[nike]]></category>
		<category><![CDATA[pc]]></category>
		<category><![CDATA[physical jerks]]></category>
		<category><![CDATA[up]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2905</guid>
		<description><![CDATA[After receiving our fifth Jawbone UP, we decided to seriously look into the newest competitor in the self-monitoring gadget race: the Nike+ FuelBand. Unfortunately, as very new accessory on the market with a fair degree of demand, it wasn&#8217;t immediately available, so we had to wait several weeks before stock was replenished. In the meantime, [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="A" class="cap"><span>A</span></span>fter receiving our fifth Jawbone UP, we decided to seriously look into the newest competitor in the self-monitoring gadget race: the Nike+ FuelBand. Unfortunately, as very new accessory on the market with a fair degree of demand, it wasn&#8217;t immediately available, so we had to wait several weeks before stock was replenished.</p>

<p>In the meantime, we looked up Nike&#8217;s sizing guide for the FuelBand, which came up short. It simply wasn&#8217;t clear from any of Nike&#8217;s documentation what size we should aim for. We printed out Nike&#8217;s sizing band, wrapped it around our wrist, and found that we literally fell on-the-line between two sizes. Per Nike&#8217;s Twitter feed, we were told that customers should opt to size up if this happens, so that&#8217;s what we did.</p>

<p>When we heard that stock was available, we made our purchase at the Nike online store. We received our FuelBand about a week later. It was packaged nicely, vaguely like you&#8217;d expect an Apple device to be boxed, but perhaps with a bit more box than necessary. In addition to the band, the box included a charging cable, a link removal tool, an 8mm extension link, a 16mm extension link, and a stand.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup></p>

<p>One link was already in the band when it arrived, and because we fell between sizes, we knew we&#8217;d have to remove it in order to get a good fit. This was an easy task, but unfortunately the sizing still seemed off &#8211; the band proved very loose even with neither of the additional links installed. If we were to wear the band <em>over</em> a sweatshirt, the fit would be great, but as it was, the band slid up and down our wrist a bit too much. It felt a bit awkward when it slid up our forearm, and when it slid down to our wrist, it hindered our full range of movement.</p>

<h3>That&#8217;s a design issue.</h3>

<p>When we bought the Jawbone UP last year, we questioned why the band didn&#8217;t link at both ends, and wished that one end could plug into the other in order to close the band securely. This is how the FuelBand works, and while we like it in theory, it&#8217;s problematic. If the Jawbone UP slides down to the base of our hand, it doesn&#8217;t restrict wrist movement because the band&#8217;s two ends can flex away from one another when pressure is applied.</p>

<p>Practically speaking, let&#8217;s take a power clean as an example. Your hands are pointed down at the ground when you start, so whatever fitness band you&#8217;re wearing is likely to slip towards the ground. If it slips enough to cover the joint of your hand and wrist, you have a problem as you continue your movement. By the time you jerk the bar from the ground and manipulate it to fall on your shoulders, your wrists should be bent backwards. If you&#8217;re wearing the FuelBand in this example, one hand won&#8217;t be able to bend back as far as the other because the band is in the way. At best, this causes some discomfort in your wrist. At worst, it throws your exercise off entirely.</p>

<p>If you&#8217;re doing the same exercise with the Jawbone UP, as soon as you bend your wrist, the two ends of the UP push away and the band slightly increases in size because of its elasticity. No harm, no foul.</p>

<p>It wasn&#8217;t until <em>after</em> we exercised with the FuelBand that we truly appreciated Jawbone&#8217;s design. In fact, before this, we cursed the design every time we accidentally tore the UP from our wrist when pulling off a sweater. Yet, it&#8217;s the very fact that the UP <em>isn&#8217;t</em> securely latched to your wrist that makes it such a great accessory for the weight room.</p>

<p>Back to sizing, we later found out that Nike claims the small FuelBand to be 171mm around with both links in, and the mediam FuelBand to be 172mm around with no links in. Yet, for some reason, Nike doesn&#8217;t recommend both links to be used at one time, which seems a little odd. This means that if we do drop down a size, we&#8217;ll have to make due with a band that&#8217;s 9mm shorter than the one we tried out. We can probably make due, even if the fit will be snug, but this likely wouldn&#8217;t correct the issue with the band restricting wrist movement, unless the band is so snug that it won&#8217;t slide over our wrist&#8217;s joint bones. Unfortunately, that means the band would have to be almost exactly the circumference of our wrists, and we seriously question the liklihood of that scenario.</p>

<h3>Otherwise, it&#8217;s pretty good.</h3>

<p>Beyond that one issue, the FuelBand&#8217;s design is pretty nice. The display is pretty much invisible until you press the one button on the surface of the device, giving the band a very plain, but sporty look. The FuelBand should really come in several colours, but they&#8217;d likely have to be dark for the LEDs to look nice and crisp, as they do on the black band. We found the addition of a time-keeping function a nice touch, as the FuelBand can easily replace a watch in the workplace. As the band is extremely plain looking, it wouldn&#8217;t even look out-of-place wearing a suit-and-tie. In contrast, the Jawbone UP&#8217;s slimmer profile, patterned surface, and unconventional parallel ends, make it stick out a lot more in a conservative workplace.</p>

<p>As far as getting the FuelBand working, there&#8217;s an additional step or two over the Jawbone UP. As we prefer to sync with the iPhone, we were disappointed that the FuelBand doesn&#8217;t work with the iPhone out-of-box. First, the FuelBand didn&#8217;t come charged, whereas the Jawbone UP ships with <em>some</em> level of power, even if low. Second, you <em>have</em> to first connect the FuelBand to a PC, after downloading the respective software application. Only once the FuelBand is set up on the PC can you set up the FuelBand app on your iPhone.</p>

<p>This wouldn&#8217;t be half bad if the FuelBand didn&#8217;t occasionally require reconnecting it to your PC. We love the convenience of syncing the FuelBand with our iPhone over Bluetooth, but after one particular sync cycle, we were told that there was inconsistent information on the device, and that we should sync with our PC to fix this.</p>

<p>The Bluetooth syncing really is nice, though. The best part is that it can sync in real time when the app is running. So <em>as you run</em>, the app updates with the activity you&#8217;re doing. You don&#8217;t <em>need</em> this functionality because you can just as easily look down at your wrist after pressing the button on the FuelBand, but presumably there are instances where looking at your iPhone is more convenient than looking at your wrist. Maybe you&#8217;re on a treadmill, for example, and your phone is propped up already.</p>

<p>The FuelBand&#8217;s accuracy is about on par with the Jawbone UP.<sup id="fnref:2"><a href="#fn:2" rel="footnote">2</a></sup> We don&#8217;t know how Nike&#8217;s tracking algorithm incorporates information on which wrist you wear the FuelBand on, but because you specify this, presumably there&#8217;s some accuracy correction for certain movements. Yet, we don&#8217;t recall ever entering into the app any information on whether we&#8217;re left or right-handed, so it&#8217;s not clear what the FuelBand is factoring in here. Otherwise, we could see it not counting certain movements we do throughout the day, like pushing our PC&#8217;s mouse around with our dominant hand.</p>

<p>As we mentioned in a previous post, the very fact the FuelBand has Bluetooth may make wearing it situationally dependent. While you can turn Bluetooth  on the FuelBand off, the very fact that the device <em>has</em> Bluetooth means certain individuals may not be able to wear it to the office.<sup id="fnref:3"><a href="#fn:3" rel="footnote">3</a></sup></p>

<p>A lot of people have discussed Nike Fuel, the unit the FuelBand tracks. This seems mostly marketing hype, however. While the FuelBand does provide a Nike Fuel reading, it also tracks and reports steps and estimated calories burned. Presumably, the app computes Fuel based on a function of steps taken over time; the more steps taken in a shorter amount of time, the higher the Fuel calculation. We hoped to play with this theory some more, but stopped using the FuelBand because of its loose fit before we could experiment enough.</p>

<h3>What it <em>doesn&#8217;t</em> have.</h3>

<p>After thinking about our band&#8217;s sizing, our first instinct was to just exchange the band for a smaller one. But as we went back to rely on the Jawbone UP exclusively again, we realized that the UP&#8217;s killer feature isn&#8217;t in tracking steps taken, it&#8217;s in the sleep alarm and night-time sleep tracker.</p>

<p>That is to say, as much as the FuelBand competes with the UP, the UP is really a different product, aimed at more general lifestyle tracking. In our case, we place a more emphasis on the sleep-related features than we do the day-time step tracking, so we realized the FuelBand will never <em>entirely</em> replace the UP unless it improves its software options.<sup id="fnref:4"><a href="#fn:4" rel="footnote">4</a></sup></p>

<p>For us, then, as long as we have an UP band that <em>works</em>, it will likely trump the FuelBand as our daily tracking accessory.<sup id="fnref:5"><a href="#fn:5" rel="footnote">5</a></sup></p>

<h3>Should you get it?</h3>

<p>The FuelBand is $50 more expensive than the UP, yet unlike with the UP, there&#8217;s no record of defective devices. If you&#8217;re big on cardio and that&#8217;s the type of movement you want to track, the FuelBand is a better option, as it tracks both steps taken and Nike Fuel, the latter which may be a better assessment of the fitness you&#8217;re getting day-by-day. If you&#8217;re already using Nike+ to track runs, then the FuelBand will fit into your workflow nicely.</p>

<p>If you plan to track your workouts in the weightroom, or where you&#8217;re otherwise manipulating your wrists (like in certain Crossfit movements), the UP may be a better option for you. And if your goal is to track more than just exercise, the FuelBand will obviously fall short.</p>

<p>Finally, if you&#8217;re considering the FuelBand, make sure you get your sizing right. The sizing does not match up with the UP (i.e. a medium in the UP is not a medium in the FuelBand), and the UP provides more flexibility despite not having removable links. If you can wait, delay a purchase until you can find the FueldBand in a local store, so you can ensure the sizing is proper. Otherwise, you may have to deal with shipping returns, which are always a hassle.</p>

<p>If it weren&#8217;t for the issues Jawbone&#8217;s had with the UP, we&#8217;d recommend it immediately. Since it&#8217;s still unclear where the UP stands regarding these problems, however, the FuelBand is a good alternative, and arguably a much better option if you&#8217;re primarily looking to track runs. If that&#8217;s not the case, you might want to hold off and see if Jawbone&#8217;s UP manufacturing is back on track, as we think more thought went into the design of the UP than the FuelBand.<sup id="fnref:6"><a href="#fn:6" rel="footnote">6</a></sup></p>

<p>Either way, for general movement tracking, the FuelBand and UP are both good devices. It&#8217;s just too bad we can&#8217;t have the best parts of each in one band.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2012/02/29/jawbone-up-trilogy/" rel="bookmark" title="February 29, 2012">Our Jawbone UP trilogy.</a> &#8211; Two months ago, we reported on the death of our Jawbone UP. It lasted longer than other folks&#8217; units&#8230;</li>

<li><a href="http://beastwith.in/2012/03/29/fourth-jawbone-up-dead/" rel="bookmark" title="March 29, 2012">Our fourth Jawbone up, dead.</a> &#8211; When we last reported on our experience with the Jawbone UP, we had just received our third band, ho&#8230;</li>

<li><a href="http://beastwith.in/2012/05/07/jawbone-up-replacement-bands-duds/" rel="bookmark" title="May 7, 2012">Jawbone UP replacement bands are duds.</a> &#8211; After weeks of use, our fourth Jawbone UP replacement band, and fifth UP overall, has finally died. &#8230;</li>
</ul>

<!-- Similar Posts took 8.970 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>We found the stand to be a bit silly, as there&#8217;s little need to prop the band up while it&#8217;s charging. Maybe some people feel they <em>need</em> a stand for every accessory they buy, but that seems a little odd.&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:2">
<p>The FuelBand was always within 100 steps of the UP.&#160;<a href="#fnref:2" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:3">
<p>Take, for example, individuals with a security clearance who work at classified facilities.&#160;<a href="#fnref:3" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:4">
<p>With the exception of the silent alarm, the FuelBand <em>could</em> track sleep. There&#8217;s an API available for the FuelBand, so someone would simply need to write an app to analyze the FuelBand&#8217;s readings at night.&#160;<a href="#fnref:4" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:5">
<p>We considered just wearing the FuelBand during the day, and the UP at night, but we&#8217;d sooner rely on only one device than two.&#160;<a href="#fnref:5" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:6">
<p>It&#8217;s Jawbone&#8217;s <em>implementation</em> of the ideas that fell short on the technical, manufacturing, end.&#160;<a href="#fnref:6" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/04/29/nike-fuelband-jawbone-up/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The theoretical 7.85&#8243; Apple tablet.</title>
		<link>http://beastwith.in/2012/04/06/theoretical-7-85-apple-tablet/</link>
		<comments>http://beastwith.in/2012/04/06/theoretical-7-85-apple-tablet/#comments</comments>
		<pubDate>Fri, 06 Apr 2012 20:06:48 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[tablets]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2892</guid>
		<description><![CDATA[Some have made the case, admittedly admirably, that if Apple were to make a tablet smaller than the iPad, it would come in at 7.85&#8243;. Technically this makes sense, but it&#8217;s only looking at the issue from a hardware perspective, not from a functional one. Take the iPhone and iPad for instance.1 The two devices [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="S" class="cap"><span>S</span></span>ome have made the case, admittedly admirably, that <em>if</em> Apple were to make a tablet smaller than the iPad, it would come in at 7.85&#8243;. <em>Technically</em> this <a href="http://goo.gl/cSqeb">makes sense</a>, but it&#8217;s only looking at the issue from a hardware perspective, not from a <em>functional</em> one.</p>

<p>Take the iPhone and iPad for instance.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup> The two devices are extremely similar on a technical level, with neither really beating the other out insofar as <em>general</em> use goes. That is to say, the iPhone can do more or less what the iPad can, and vice versa. The only major caveat here is that the iPhone is a <em>phone</em>, and the iPad is <em>larger</em>.<sup id="fnref:2"><a href="#fn:2" rel="footnote">2</a></sup> And it&#8217;s the latter point we&#8217;ll focus on, because <em>size</em> in this regard is important.</p>

<p>The iPhone and iPad are so similar that Apple-haters have called the iPad <em>nothing more than an oversized iPhone</em>. And while that&#8217;s somewhat true from a thousand-foot perspective, it&#8217;s tough to argue that iPad and iPhone sales are cannibalizing one another, especially when so many owners of one also own the other.</p>

<h3>Why is that?</h3>

<p>It&#8217;s a matter of use, and environment is only one factor. For example, we use TweetBot on both our iPhone and our iPad, but <em>how</em> we use TweetBot on the two devices is somewhat different. For example, we have both apps hooked up to our Readability account, but when we come across a link to an article in our Twitter feed when we&#8217;re using TweetBot for the iPhone, we&#8217;ll typically send it to Readability to read later without even peeking at it first. On the iPad, we&#8217;ll generally click the link to the article, and either read it right then, else save it to Readability to reference at a later time. The point is, while TweetBot on both apps offers the same functionality, we&#8217;ll favor a particular workflow on one device over another, because a given device is better for some tasks depending on the <em>form</em> the device takes.</p>

<p>That&#8217;s the reason mobile versions of web sites make more sense on the iPhone. At first, we were incredibly annoyed that most mobile web site versions lacked the same features as the &#8220;full&#8221; site, but from a use scenario, most people don&#8217;t <em>need</em> access to the full site when they&#8217;re using a mobile device.<sup id="fnref:3"><a href="#fn:3" rel="footnote">3</a></sup> That&#8217;s because most people aren&#8217;t using the iPhone as their <em>primary</em> browser, but rather a <em>backup</em> browser used on the road.</p>

<p>The iPad, however, is another story. A lot of people <em>are</em> using the iPad as their primary computing device, and so expect web sites to load with all the functionality in a desktop version. That&#8217;s why it&#8217;s so important for developers to ensure that web site versions designed for viewing on phones aren&#8217;t the design that show up for tablet users: the user expectation is different.</p>

<p>There are also some apps that simply wouldn&#8217;t work on a given device, even though there&#8217;s no technical reason an app <em>couldn&#8217;t</em> be written for it. We&#8217;ve recently enjoyed sketching out some design ideas in Papers, an app made for iPad. There&#8217;s no reason the developers couldn&#8217;t make Papers into a universal app and offer an iPhone version, but it would detract from the experience; part of the joy of using Papers on an iPad is the amount of drawing real-estate available to the user, and decreasing this real-estate would make for a less-enjoyable experience. In fact, this the reason we don&#8217;t see the type of drawing apps on iPhones as we do on the iPad: the iPhone&#8217;s screen is too small to be of any real use to artists.</p>

<h3>What does this have to do with a smaller iPad?</h3>

<p>Whether or not Apple can release a 7.85&#8243; tablet without annoying developers, there&#8217;s nothing a 7.85&#8243; tablet would do that the iPhone and iPad can&#8217;t, on both a technical level and a task-specific one. Whereas we&#8217;ve illustrated how workflows can change depending on whether you&#8217;re using an app on an iPhone or iPad, and how some apps simply make more sense on one form factor, what makes <em>best</em> sense on a 7.85&#8243; tablet? <em>Nothing</em>.</p>

<p>A 7.85&#8243; tablet would be too small for gaining the major benefits of apps like Papers, and too big to be an always-available backup device for checking mail, Twitter, etc. Our use of TweetBot on this imaginary 7.85&#8243; device would either mimic our use of TweetBot on the iPhone or iPad, but not differ the way it does between version now. No matter what kind of an app you can think of, the app will always suit an iPhone or iPad <em>better</em>.</p>

<p>A 7.85&#8243; device simply makes no sense in this market, and we don&#8217;t even need to argue costs to make that case.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2011/04/12/ipad-post-pc-device/" rel="bookmark" title="April 12, 2011">The iPad as post-PC device.</a> &#8211; Michael Gartenberg clarifies Steve Jobs&#8217; statement that the iPad is a post-PC device by [pointing ou...</li>

<li><a href="http://beastwith.in/2011/10/10/siri-integration-with-the-apple-tv/" rel="bookmark" title="October 10, 2011">Siri integration with the Apple TV?</a> - Microsoft recently sent out a heads-up to the masses that XBox Live will undergo [another update](ht&#8230;</li>

<li><a href="http://beastwith.in/2010/03/29/the-ipad-should-interface-with-the-iphone-directly/" rel="bookmark" title="March 29, 2010">The iPad should interface with the iPhone directly.</a> &#8211; As we checked out Apple&#8217;s latest guided tours for the iPad, it occurred to us that since the iPad is&#8230;</li>
</ul>

<!-- Similar Posts took 10.768 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>We&#8217;re lumping the iPod Touch in the with the iPhone, for the sake of simplicity.&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:2">
<p>Since Siri is technically still in <em>beta</em>, we won&#8217;t consider Siri a worthwhile caveat in this argument. After all, despite the fact that Apple heavily marketed Siri with the iPhone 4S, Siri is non-existent on the other two iPhone models sold today; Siri is less an argument for the iPhone than it is the iPhone <em>4S</em>.&#160;<a href="#fnref:2" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:3">
<p>Though, we still maintain that users should have the option of loading a full site on an iPhone if requested, in the event they <em>do</em> need specific functionality.&#160;<a href="#fnref:3" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/04/06/theoretical-7-85-apple-tablet/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Our fourth Jawbone up, dead.</title>
		<link>http://beastwith.in/2012/03/29/fourth-jawbone-up-dead/</link>
		<comments>http://beastwith.in/2012/03/29/fourth-jawbone-up-dead/#comments</comments>
		<pubDate>Thu, 29 Mar 2012 18:43:10 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[accesories]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[jawbone]]></category>
		<category><![CDATA[up]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2886</guid>
		<description><![CDATA[When we last reported on our experience with the Jawbone UP, we had just received our third band, hoping it would last longer than the one we originally purchased. It turns out it didn&#8217;t, as the vibration motor died shortly after our post went up. This meant the alarm function was useless, so we sent [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="W" class="cap"><span>W</span></span>hen we last reported on our experience with the Jawbone UP, we had just received our third band, hoping it would last longer than the one we originally purchased. It turns out it didn&#8217;t, as the vibration motor died shortly after <a href="http://beastwith.in/2012/02/29/jawbone-up-trilogy/">our post</a> went up. This meant the alarm function was useless, so we sent another e-mail to Jawbone support, and were told they would send us a <em>fourth</em> band.</p>

<p>It took about three weeks to get the new band in our hands, with Jawbone being a bit less responsive about getting an RMA and tracking number to us, compared to how they handled our earlier replacements. We asked Jawbone support whether the fourth band they were to send us was part of the original production run, or if it was manufactured afterwards and with updates addressing earlier problems. What we got was a bland reply not really addressing the question:</p>

<blockquote>
  <p>We are committed to send a brand new fully working band, if you have any issue with this new band you can just contact us and we will be glad to replace it for you again.</p>
</blockquote>

<p>We received our fourth band, and after a full charge and a day&#8217;s use, the band reported 58% battery life left. The next evening, about 38%. The third evening, 20%. The band died that night, so our alarm never went off.</p>

<p>After trying to charge the UP, the band quickly showed the white light indicating the band was full, and no matter how long we kept the UP band plugged in, it refused to sychronize with our iPhone. So this morning, we sent yet another e-mail to Jawbone, explaining that this fourth band didn&#8217;t even last a full week.</p>

<p>Our experience with the UP has gone downhill since the original band we purchased; our replacement bands have actually failed in <em>less</em> time than the original band, so we assume they&#8217;re all part of the original production run and Jawbone is simply getting rid of the stock they have left. Presumably, a lot of other UP buyers have taken their refunds and not bothered to obtain replacement bands, and since Jawbone isn&#8217;t currently selling them, they undoubtedly have stock that needs to either be thrown away, else <em>given</em> away. Unfortunately, we&#8217;d prefer the former, because continuing to send out bands that are prone to fail isn&#8217;t going to help smooth over relations with already upset customers.</p>

<p>Per one of Jawbone&#8217;s earlier responses, they will keep sending out replacement bands for as long as the original band&#8217;s warranty is for. That doesn&#8217;t make us feel much better.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2012/05/07/jawbone-up-replacement-bands-duds/" rel="bookmark" title="May 7, 2012">Jawbone UP replacement bands are duds.</a> &#8211; After weeks of use, our fourth Jawbone UP replacement band, and fifth UP overall, has finally died. &#8230;</li>

<li><a href="http://beastwith.in/2011/12/30/heres-to-jawbones-customer-service/" rel="bookmark" title="December 30, 2011">Here&#8217;s to Jawbone&#8217;s customer service.</a> &#8211; As a followup to our last post on the Jawbone UP, we thought it appropriate to provide an update to &#8230;</li>

<li><a href="http://beastwith.in/2012/02/29/jawbone-up-trilogy/" rel="bookmark" title="February 29, 2012">Our Jawbone UP trilogy.</a> &#8211; Two months ago, we reported on the death of our Jawbone UP. It lasted longer than other folks&#8217; units&#8230;</li>
</ul>

<!-- Similar Posts took 7.804 ms -->
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/03/29/fourth-jawbone-up-dead/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Retina graphics and file-sizes.</title>
		<link>http://beastwith.in/2012/03/23/retina-graphics-file-sizes/</link>
		<comments>http://beastwith.in/2012/03/23/retina-graphics-file-sizes/#comments</comments>
		<pubDate>Fri, 23 Mar 2012 21:59:14 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[iOS]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[ipod]]></category>
		<category><![CDATA[retina]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2883</guid>
		<description><![CDATA[Retina-optimized graphics are awesome, we all pretty much agree. But there comes a trade-off with such: file-size. TUAW&#8217;s Mike Schramm summarizes the issue: The most obvious drawback is app size. Those bigger graphics take up more space, and for many graphics-heavy applications, that could put them over the cellular data download limit (now at 50 [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="R" class="cap"><span>R</span></span>etina-optimized graphics are awesome, we all pretty much agree. But there comes a trade-off with such: file-size. TUAW&#8217;s Mike Schramm <a href="http://www.tuaw.com/2012/03/20/the-trouble-with-universal-and-the-new-ipad/">summarizes the issue</a>:</p>

<blockquote>
  <p>The most obvious drawback is app size. Those bigger graphics take up more space, and for many graphics-heavy applications, that could put them over the cellular data download limit (now at 50 MB). Universal apps specifically are taking this hit, even if they&#8217;re not running with the new iPad-sized graphics on the iPhone hardware.</p>
</blockquote>

<p>A good universal app today supports four resolutions:</p>

<ol>
<li>Legacy graphics for the 2G iPhone, iPhone 3/3GS, and iPod Touch.</li>
<li>Legacy graphics for the original iPad and iPad 2.</li>
<li>Retina graphics for the iPhone 4/4S.</li>
<li>Retina graphics for the new iPad.</li>
</ol>

<p>There are ways to mitigate the file size increase, such as recycling retina iPhone graphics for use on older iPads. In search of real-life examples for how an app is distributed, however, Lex Friedman at MacWorld <a href="http://www.macworld.com/article/1165797/retina_display_ready_apps_and_the_coming_ipad_storage_crunch.html">compared the pre-retina and post-retina</a> file sizes of Apple&#8217;s own universal iOS apps. In doing so, we see file sizes roughly 2.75 times greater post-retina.</p>

<p>Between this, camera improvements, and more computing power to push more detailed textures in 3D games, there&#8217;s a reason the 16GB new iPad isn&#8217;t recommended by a lot of bloggers.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup></p>

<p>While we can assume that support for older devices will drop in the future, we still have at least a generation or two to go before non-retina devices are no longer supported by new versions of iOS. And even when that time comes, dropping non-retina graphics files won&#8217;t drastically improve the footprint of app file sizes, since it&#8217;s the retina versions that are making file sizes much bigger. At the very least, we should expect next year&#8217;s iPad to offer a 128GB storage option.</p>

<p>In the meantime, we still maintain that better cloud tools would help immensely, especially with large iPhoto libraries that can take up considerable storage space. Another potential solution on Apple&#8217;s side is to somehow strip graphics from AppStore downloads that aren&#8217;t needed on a target device. For example, retina graphics would be removed from an app downloaded from a non-retina device, and iPad graphics would be stripped from a universal app if installed on an iPhone.</p>

<p>Then again, perhaps we&#8217;re making too large an issue out of one that&#8217;s easily rectified in one or two generations, as flash storage becomes cheaper. Still, it&#8217;s enough of a problem that some are pushing <em>not</em> to release universal apps in order to save on storage space, a proposal that we find to be a rather bittersweet solution.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2011/06/23/apples-console-already-exists/" rel="bookmark" title="June 23, 2011">]\</a> &#8211; We&#8217;ve been somewhat critical of the Apple TV as a gaming console, and when [we last wrote about the &#8230;</li>

<li><a href="http://beastwith.in/2010/12/17/ipad-second-generation/" rel="bookmark" title="December 17, 2010">iPad, the second generation.</a> &#8211; Plenty of rumours about iPad 2.0 are hitting the blogosphere, complete with photos of &#8220;leaks&#8221; from c&#8230;</li>

<li><a href="http://beastwith.in/2011/03/11/why-we-probably-wont-get-an-ipad-2/" rel="bookmark" title="March 11, 2011">Why we probably won&#8217;t get an iPad 2.</a> &#8211; We say &#8220;probably&#8221; because if Target doesn&#8217;t have a line at 17:00 today, we may be tempted to stop in&#8230;</li>
</ul>

<!-- Similar Posts took 10.626 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>We&#8217;d only recommend the 16GB version for those who primarily only surf the web and use a small number of apps. For the average user, 32GB sounds about right, while 64 GB is probably a little too much, and barely adequate for advanced users.&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/03/23/retina-graphics-file-sizes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Day One to track specific activities.</title>
		<link>http://beastwith.in/2012/03/20/using-day-one-track-specific-activities/</link>
		<comments>http://beastwith.in/2012/03/20/using-day-one-track-specific-activities/#comments</comments>
		<pubDate>Tue, 20 Mar 2012 18:37:37 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[dropbox]]></category>
		<category><![CDATA[icloud]]></category>
		<category><![CDATA[iOS]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[lifestyle]]></category>
		<category><![CDATA[os x]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2881</guid>
		<description><![CDATA[Every couple weeks we read about someone else taking up a private journal with Day One, a journaling app available for both iOS and OS X. One of the key benefits of the app is its cloud-based synchronization, allowing you to use iCloud or Dropbox to keep entries updates across devices. The app is also [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="E" class="cap"><span>E</span></span>very couple weeks we read about someone else taking up a private journal with Day One, a journaling app available for both iOS and OS X. One of the key benefits of the app is its cloud-based synchronization, allowing you to use iCloud or Dropbox to keep entries updates across devices. The app is also acknowledged for its rather good-looking interface, which sets it apart from similar apps available in the App Store.</p>

<p>We picked up Day One for iOS several months back, but didn&#8217;t use it too extensively.We&#8217;ve wanted to keep a private journal for many years now, but find that we never etch enough time into our schedule to make it happen.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup></p>

<p>Day One is fairly simplistic as far as journaling apps go. There&#8217;s limited Markdown support at the moment, and no integration with social networking sites, nor with embedded media outside of hyperlinks. In a way, that&#8217;s one of Day One&#8217;s strengths, because it focuses you on <em>writing</em>, not reviewing what you posted on Twitter earlier that day, or where you checked in via FourSquare.<sup id="fnref:2"><a href="#fn:2" rel="footnote">2</a></sup></p>

<p>Where we&#8217;ve found Day One to excel is in writing short journal entries and tracking some amount of information we&#8217;d otherwise lose sight of. For example, we&#8217;ve used other apps to track lifestyle activities like meals eaten, workout results, and general physical condition. These tend to be activity-specific apps, like Livestrong&#8217;s MyPlate, or Azumio&#8217;s Heart Rate monitor. Day One allows us to compile all this information into one daily log, which may not offer fancy graphs for tracking this data visually, but still serves as a useful log for later reference.</p>

<p>It&#8217;d be great if the various tracking apps we use could easily export to Day One using a URL scheme,<sup id="fnref:3"><a href="#fn:3" rel="footnote">3</a></sup> but Launch Center already supports starting a new Day One entry with clipboard information, so as long as a given tracking app will let you copy information to the clipboard, a simple workflow follows accordingly.<sup id="fnref:4"><a href="#fn:4" rel="footnote">4</a></sup></p>

<p>While we&#8217;re still not using Day One for longform entries, the app remains on our iPhone and iPad to track other daily notes, likes foods eaten and how we felt accordingly thereafter. It&#8217;s great for this, and we wonder why we didn&#8217;t think of using Day One to journal these types of activities earlier.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2012/03/30/more-keyboards-ipads/" rel="bookmark" title="March 30, 2012">More on keyboards and iPads.</a> &#8211; One of the iPad&#8217;s greatest strengths is its touch interface, which has proven itself more intuitive &#8230;</li>

<li><a href="http://beastwith.in/2011/11/07/first-take-on-the-jawbone-up/" rel="bookmark" title="November 7, 2011">First take on the Jawbone UP.</a> &#8211; On Friday, we drove by two Targets, a Best Buy, and an AT&#038;T store to see if anyone was selling the J&#8230;</li>

<li><a href="http://beastwith.in/2011/05/11/apps-that-tell-you-where-the-po-po-is/" rel="bookmark" title="May 11, 2011">Apps that tell you where the po-po is.</a> &#8211; Apple is being asked by the U.S. Senate why they haven&#8217;t removed iOS apps from the AppStore that rep&#8230;</li>
</ul>

<!-- Similar Posts took 9.470 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>We toyed with the idea of using it to store blog entries too, but ultimately decided it slowed down our workflow.&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:2">
<p>There&#8217;s also no search function yet, which is the best indicator that reviewing content was not the developer&#8217;s primary objective for the app. Hopefully it will come soon, however.&#160;<a href="#fnref:2" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:3">
<p>DayOne already supports URL schemes, so it&#8217;s just a matter of third-parties adding support.&#160;<a href="#fnref:3" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:4">
<p>Unfortunately, none of the tracking apps we use will export daily information to even the clipboard, so we&#8217;re currently summarizing things manually in Day One. We may look into replacing some of these apps to see if an alternative with exporting exists.&#160;<a href="#fnref:4" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/03/20/using-day-one-track-specific-activities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Personal computing</title>
		<link>http://beastwith.in/2012/03/10/personal-computing/</link>
		<comments>http://beastwith.in/2012/03/10/personal-computing/#comments</comments>
		<pubDate>Sat, 10 Mar 2012 18:00:03 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[ipod]]></category>
		<category><![CDATA[tablets]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2871</guid>
		<description><![CDATA[We expect that a lot of people don&#8217;t know what &#8220;PC&#8221; stands for, or at least give it any real thought. The idea of a &#8220;personal computer&#8221; came about at a time when computers were huge, expensive, and used by several people in research facilities and universities. At the time, what made a computer &#8220;personal&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="W" class="cap"><span>W</span></span>e expect that a lot of people don&#8217;t know what &#8220;PC&#8221; stands for, or at least give it any real thought. The idea of a &#8220;personal computer&#8221; came about at a time when computers were huge, expensive, and used by several people in research facilities and universities. At the time, what made a computer &#8220;personal&#8221; was that it was owned by a person instead of a company or organization. As more and more people relied on desktop computers at home, the &#8220;personal&#8221; half of the term had less and less meaning; in homes where several family members used a computer, the desktop and file structure became a mish-mash of the user&#8217;s personalities. Things changed a bit when home operation systems began to use local accounts, one for each user. But even then, the form factor of a typical computer simply doesn&#8217;t lend itself to the level of connectivity that something &#8220;personal&#8221; ought to.</p>

<p>Compare this to an iPod, for example. An iPod is cheap enough for most everyone to own, and its contents are a reflection of the owner, containing her tastes, styles, and interests. Even the exterior of the device can be customized by the owner, either by choosing a specific exterior color at purchase, else using cases and decals. Furthermore, the form factor of an iPod is perfect; most people can use their iPod at home, on their commute, at work, and in the gym.</p>

<p>While computers have become smaller, and notebooks more common, they still don&#8217;t reach the level of closeness that people have with their iPods, because they&#8217;re still very task-specific tools.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup> This is where mobile devices have stepped in to become the <em>everywhere</em> tool in a person&#8217;s life. While smartphones have been reasonably successful, their size makes certain tasks limited, or cumbersome. To great success, the iPad has found the middle road between what&#8217;s small enough to go most everywhere and what&#8217;s large enough to still be useful for most tasks. And the iPad form factor, a tablet, makes it ideal for tasks that most people would never have considered doing on a computer, or on a mobile device.</p>

<p><a href="http://512pixels.net/ipad-usage/">Stephen Hackett comments</a> on several tasks he uses his iPad for:</p>

<blockquote>
  <p>I can do all of these things on my MacBook Pro, or even my Mac mini at home. The iPad, however, makes these tasks not only easier, but more enjoyable … especially on the couch, with a beer.</p>
</blockquote>

<p>The success of the iPad isn&#8217;t in just in what all it can do, because contrary to what some may claim, the iPad is not &#8220;just another tool&#8221;. Rather, the iPad is successful because not only does it do a lot, but it lets you integrate the iPad into all your daily tasks, be it in the kitchen, at the office, on the couch, or even in the bathroom. The iPad is a more natural fit for how we live our lives, instead of constraining our tasks to a necessary time and place that most traditional computers require.</p>

<p>If anything, the iPad is a <em>more</em> personal computer than a PC, which is really what this &#8220;post-PC&#8221; hub-bub in the press is all about. &#8220;PC&#8221; has become a misnomer, because compared to the iPad and its emulators, PCs are <em>not</em> personal, they&#8217;re <em>impersonal</em>.<sup id="fnref:2"><a href="#fn:2" rel="footnote">2</a></sup> Inasmuch as what the iPad can <em>do</em>, it may differ little from a conventional PC, but the idea Apple is pushing with their post-PC nomenclature is that tablets are opening new doors for how computers can be used, and it&#8217;s about as drastic as the difference was between PCs and what came before.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2012/04/06/theoretical-7-85-apple-tablet/" rel="bookmark" title="April 6, 2012">The theoretical 7.85&#8243; Apple tablet.</a> &#8211; Some have made the case, admittedly admirably, that _if_ Apple were to make a tablet smaller than th&#8230;</li>

<li><a href="http://beastwith.in/2011/04/12/ipad-post-pc-device/" rel="bookmark" title="April 12, 2011">The iPad as post-PC device.</a> &#8211; Michael Gartenberg clarifies Steve Jobs&#8217; statement that the iPad is a post-PC device by [pointing ou&#8230;</li>

<li><a href="http://beastwith.in/2011/02/22/the-ipad-cant-do-work/" rel="bookmark" title="February 22, 2011">The iPad can&#8217;t do work?</a> &#8211; We&#8217;ve already written about our iPad serving as a Mac replacement for most tasks, but there&#8217;s still &#8230;</li>
</ul>

<!-- Similar Posts took 11.918 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>Among nerds, this is somewhat less true, because they use their computers to do more.&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:2">
<p>If only we could rebrand PCs of yesterday as IPCs, and call tablets PCs instead.&#160;<a href="#fnref:2" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/03/10/personal-computing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AT&amp;T data throttling is wrong.</title>
		<link>http://beastwith.in/2012/03/09/att-data-throttling-wrong/</link>
		<comments>http://beastwith.in/2012/03/09/att-data-throttling-wrong/#comments</comments>
		<pubDate>Fri, 09 Mar 2012 20:01:31 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[at&t]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[iphone]]></category>

		<guid isPermaLink="false">http://beastwith.in/?p=2870</guid>
		<description><![CDATA[When the original iPad was released, the 3G version was exclusive to AT&#38;T. Among the data plans offered was an &#8220;unlimited&#8221; plan that ran for $29.99/month. This plan has since been deprecated; if you bought an iPad after the plan was discontinued, you have to opt for a limited bandwidth tier, while those who had [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="W" class="cap"><span>W</span></span>hen the original iPad was released, the 3G version was exclusive to AT&amp;T. Among the data plans offered was an &#8220;unlimited&#8221; plan that ran for $29.99/month. This plan has since been deprecated; if you bought an iPad after the plan was discontinued, you have to opt for a limited bandwidth tier, while those who had the option for the unlimited plan before are grandfathered in. Today, the largest data plan available through AT&amp;T is 3GB/month, with additional bandwidth costing extra.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup> Conveniently, the 3GB plan also costs $29.99/month.</p>

<p>The controversy with the unlimited plan is that AT&amp;T has threatened to throttle bandwidth for unlimited plan subscribers for quite some time. Reports have been varied, and customers wanted a clarification of the rule. Recently, AT&amp;T <a href="http://hothardware.com/News/ATT-Clarifies-Data-Limitations-on-Unlimited-Data-Plans/">provided this clarification</a>, stating they would throttle bandwidth for all unlimited plan subscribers after 3GB of bandwidth is consumed in a given month. Once the next billing cycle begins anew, the throttle would be removed, and customers would be back to full-speed data transfers. AT&amp;T&#8217;s argument is that they want to ensure that a minority of users are not placing undue burden on the network for the majority, but as Hot Hardware points out, that&#8217;s not really the case:</p>

<blockquote>
  <p>First, AT&amp;T&#8217;s bandwidth throttle is based solely on a person&#8217;s usage, not their location or the overall demand for bandwidth at any given time. In reality, this is never the case. At 5PM in a downtown metropolitan area, cellular bandwidth will be at an absolute premium &#8212; a graveyard shift worker in one of the office buildings at 3 AM has no way to saturate the available spectrum, even if they had a dozen phones.</p>
</blockquote>

<p>In other words, AT&amp;T is finding a convenient excuse (that doesn&#8217;t hold much water) to charge their early iPad-adopting customers more money than they were initially led to believe. If these customers choose not to switch plans and pony up for more bandwidth in the event they exceed 3GB/month, AT&amp;T throttles the customer&#8217;s networks speed by as much as 95%, effectively making the data connection useless.<sup id="fnref:2"><a href="#fn:2" rel="footnote">2</a></sup> AT&amp;T is still <em>technically</em> providing unlimited bandwidth to the customer, only it&#8217;s at incredibly low speeds.</p>

<p>An iPhone user in California recently won a small claims court judgement for $850 over this throttling fiasco<sup id="fnref:3"><a href="#fn:3" rel="footnote">3</a></sup>, and I would be surprised if others don&#8217;t take similar legal actions. Not everyone sees the small claims court victory just, however, <a href="http://www.splatf.com/2012/03/att-throttling/">like Dan Frommer</a>:</p>

<blockquote>
  <p>Please get over your emotional battle — and extinguish any legal threats, that’s silly — and join us in reality. If you use a lot of mobile data, be happy about it, and be happy paying for it.</p>
</blockquote>

<p>Dan&#8217;s argument is just as emotional as the argument of those asking that &#8220;unlimited&#8221; mean &#8220;unlimited bandwidth at maximum speed&#8221;; Dan accuses unlimited subscribers of whining, but then whines about how we&#8217;re all hurting his precious network. But as Hot Hardware points out, high-bandwidth users aren&#8217;t necessarily adversely affecting the network; for AT&amp;T to justly throttle a user&#8217;s speeds, the burden of proof needs to be on them to show that a user&#8217;s network use was affecting the network in a negative way, but they&#8217;re not doing that. The <em>reality</em> is AT&amp;T trying to underhandedly change the terms of its original $29.99/month plan by convincing the majority of its customers that they would be negatively impacted otherwise.</p>

<p>The assumption Dan makes (and those who back him in this) is not just that unlimited-plan subscribers are hammering network speeds for everyone else, but that they&#8217;re <em>consistently</em> using more than 3GB of data each month. To our knowledge, AT&amp;T hasn&#8217;t provided any evidence of this either, and from an anecdotal perspective, we don&#8217;t believe this to be the case; we&#8217;ve been on the unlimited plan since pretty much day one, and most months, don&#8217;t come close to reaching 3GB.<sup id="fnref:4"><a href="#fn:4" rel="footnote">4</a></sup> We may <em>never</em> exceed the 3GB cap each month, and if we have, it&#8217;s incredibly rare. This means that most months, we pay <em>more</em> than what we use, and would be surprised to hear it&#8217;s much different for many other unlimited plan subscribers. In effect, we&#8217;re putting <em>more</em> into the network than the average consumer, and so if we happen to exceed the 3GB cap one month, shouldn&#8217;t we morally be allowed to get away with it? Maybe Dan should be <em>thanking</em> us instead of calling us whiners.</p>

<p>AT&amp;T has a rollover minutes plan for their cell phones, which seems reasonably fair: if you don&#8217;t use all your minutes in a given month, the surplus will be added to your next month&#8217;s minutes (to a limit) for you to use later. Maybe AT&amp;T should do something like this for data. But that would be <em>fair</em>.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2012/03/13/choosing-att-new-ipad/" rel="bookmark" title="March 13, 2012">Choosing AT&#038;T for the new iPad.</a> &#8211; When we pre-ordered the new iPad last week, we opted to stick with AT&#038;T for data coverage, despite o&#8230;</li>

<li><a href="http://beastwith.in/2008/07/05/getting-an-iphone-3g-sans-contract-the-costs/" rel="bookmark" title="July 5, 2008">Getting an iPhone 3G sans contract: the costs.</a> &#8211; In what should be illegal, AT&amp;T is charging $700 for a 16GB iPhone that&#8217;s not contracted to them&#8230;</li>

<li><a href="http://beastwith.in/2007/09/12/on-unlocking-my-iphone/" rel="bookmark" title="September 12, 2007">On unlocking my iPhone.</a> &#8211; Those following my Twitter status know that I finally broke down and purchased an iPhone, with the o&#8230;</li>
</ul>

<!-- Similar Posts took 12.426 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>Subscribers on the 3GB plan pay $10/GB after their base 3GB is consumed.&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:2">
<p>Throttling speeds this much means the customer is getting much less than even EDGE speeds.&#160;<a href="#fnref:2" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:3">
<p>Early iPhone adopters were also offered an unlimited plan by AT&amp;T, and are similarly grandfathered in.&#160;<a href="#fnref:3" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:4">
<p>It&#8217;s a matter of convenience for me; I don&#8217;t want to keep a close eye on the amount of data I&#8217;m using, nor risk an overage charge that would make a higher tier more practical. The iPad exemplifies ease-of-use and a no-hassle experience, and I don&#8217;t believe its data connectivity should be any different.&#160;<a href="#fnref:4" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/03/09/att-data-throttling-wrong/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Our Jawbone UP trilogy.</title>
		<link>http://beastwith.in/2012/02/29/jawbone-up-trilogy/</link>
		<comments>http://beastwith.in/2012/02/29/jawbone-up-trilogy/#comments</comments>
		<pubDate>Wed, 29 Feb 2012 20:24:16 +0000</pubDate>
		<dc:creator>WyldKard</dc:creator>
				<category><![CDATA[Techno-Shaman]]></category>
		<category><![CDATA[accessories]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[mendax.org]]></category>

		<guid isPermaLink="false">http://mendax.org/?p=2862</guid>
		<description><![CDATA[Two months ago, we reported on the death of our Jawbone UP. It lasted longer than other folks&#8217; units, but ultimately succumbed to a battery issue. Jawbone customer service was prompt in getting me a new UP, and so I didn&#8217;t have too much untracked activity time. Our second UP band had a couple hiccups [...]]]></description>
			<content:encoded><![CDATA[<p class="first-child "></p><p><span title="T" class="cap"><span>T</span></span>wo months ago, we reported on the death of our Jawbone UP. It lasted longer than other folks&#8217; units, but ultimately succumbed to a battery issue. Jawbone customer service <a href="http://beastwith.in/2011/12/30/heres-to-jawbones-customer-service/">was prompt</a> in getting me a new UP, and so I didn&#8217;t have too much untracked activity time.</p>

<p>Our second UP band had a couple hiccups since we received it. Nothing major, but the band randomly &#8220;reset&#8221; twice, requiring a sync with our iPhone to get working again. Then, about two weeks ago, the band succumbed to the same fate as our first UP. So much for Jawbone having worked out whatever issue caused the original&#8217;s death.<sup id="fnref:1"><a href="#fn:1" rel="footnote">1</a></sup></p>

<p>Customer service was again prompt, and we had an RMA number and shipping number a couple days after reporting the problem. We&#8217;re now on our third UP band. On the plus side, it means we have two replacement caps in case one gets lost<sup id="fnref:2"><a href="#fn:2" rel="footnote">2</a></sup>, but we also have two dead bands that we haven&#8217;t thrown out yet.</p>

<p>Around the time the second band died, Jawbone released an update to their iPhone software. We didn&#8217;t notice any <em>substantial</em> changes, and the food tracking log remains mostly useless. Time will tell whether the third band will last longer than two months, but we&#8217;re hoping that this time, Jawbone replaced the UP with a version that doesn&#8217;t have the same issue the earlier ones did. You&#8217;d think that at this point, they&#8217;d have done enough testing to get a longer-term solution out there.</p>

<hr />

<p><strong>Similar Posts:</strong></p>

<ul class="similar-posts"><li><a href="http://beastwith.in/2012/03/29/fourth-jawbone-up-dead/" rel="bookmark" title="March 29, 2012">Our fourth Jawbone up, dead.</a> &#8211; When we last reported on our experience with the Jawbone UP, we had just received our third band, ho&#8230;</li>

<li><a href="http://beastwith.in/2012/05/07/jawbone-up-replacement-bands-duds/" rel="bookmark" title="May 7, 2012">Jawbone UP replacement bands are duds.</a> &#8211; After weeks of use, our fourth Jawbone UP replacement band, and fifth UP overall, has finally died. &#8230;</li>

<li><a href="http://beastwith.in/2011/12/30/heres-to-jawbones-customer-service/" rel="bookmark" title="December 30, 2011">Here&#8217;s to Jawbone&#8217;s customer service.</a> &#8211; As a followup to our last post on the Jawbone UP, we thought it appropriate to provide an update to &#8230;</li>
</ul>

<!-- Similar Posts took 25.808 ms -->

<div class="footnotes">
<hr />
<ol>

<li id="fn:1">
<p>We assumed the replacement band <em>wasn&#8217;t</em> the same as those sold before the recall, but as both bands lasted a similar amount of time, both to the same issue, apparently Jawbon was just clearing out old stock.&#160;<a href="#fnref:1" rev="footnote">&#8617;</a></p>
</li>

<li id="fn:2">
<p>A concern some people have with the UP&#160;<a href="#fnref:2" rev="footnote">&#8617;</a></p>
</li>

</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://beastwith.in/2012/02/29/jawbone-up-trilogy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

