<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Finally: The End of Food Journals? The iPhone FoodScanner Arrives</title>
	<atom:link href="http://www.fourhourworkweek.com/blog/2009/09/24/finally-the-end-of-food-journals-the-iphone-foodscanner-arrives/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fourhourworkweek.com/blog/2009/09/24/finally-the-end-of-food-journals-the-iphone-foodscanner-arrives/</link>
	<description>Tim Ferriss's 4-Hour Workweek and Lifestyle Design Blog</description>
	<lastBuildDate>Fri, 19 Mar 2010 05:27:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Idea #11: A database of how items are originally packaged &#171; Ismail&#39;s Ideas</title>
		<link>http://www.fourhourworkweek.com/blog/2009/09/24/finally-the-end-of-food-journals-the-iphone-foodscanner-arrives/comment-page-1/#comment-63376</link>
		<dc:creator>Idea #11: A database of how items are originally packaged &#171; Ismail&#39;s Ideas</dc:creator>
		<pubDate>Mon, 22 Feb 2010 18:10:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.fourhourworkweek.com/blog/?p=2202#comment-63376</guid>
		<description>[...] this, create an index of products, similar to the indexes of foods at sites like StillTasty and DailyBurn. Instead of expiration dates and nutritional information, though, this should walk users through [...]</description>
		<content:encoded><![CDATA[<p>[...] this, create an index of products, similar to the indexes of foods at sites like StillTasty and DailyBurn. Instead of expiration dates and nutritional information, though, this should walk users through [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Schmitt</title>
		<link>http://www.fourhourworkweek.com/blog/2009/09/24/finally-the-end-of-food-journals-the-iphone-foodscanner-arrives/comment-page-1/#comment-61626</link>
		<dc:creator>Nathan Schmitt</dc:creator>
		<pubDate>Thu, 14 Jan 2010 06:20:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.fourhourworkweek.com/blog/?p=2202#comment-61626</guid>
		<description>Heads up Tim, video was taken down.</description>
		<content:encoded><![CDATA[<p>Heads up Tim, video was taken down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Smith</title>
		<link>http://www.fourhourworkweek.com/blog/2009/09/24/finally-the-end-of-food-journals-the-iphone-foodscanner-arrives/comment-page-1/#comment-56420</link>
		<dc:creator>Andy Smith</dc:creator>
		<pubDate>Tue, 01 Dec 2009 15:44:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.fourhourworkweek.com/blog/?p=2202#comment-56420</guid>
		<description>Dustin,

Thanks for the comments.

Re: input... next update (should be in the store any time now) will have favorites so you can easily get to the foods you eat frequently.

Calorie breakdown in FoodScanner is coming too.

Best Regards,

Andy Smith</description>
		<content:encoded><![CDATA[<p>Dustin,</p>
<p>Thanks for the comments.</p>
<p>Re: input&#8230; next update (should be in the store any time now) will have favorites so you can easily get to the foods you eat frequently.</p>
<p>Calorie breakdown in FoodScanner is coming too.</p>
<p>Best Regards,</p>
<p>Andy Smith</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Ferriss</title>
		<link>http://www.fourhourworkweek.com/blog/2009/09/24/finally-the-end-of-food-journals-the-iphone-foodscanner-arrives/comment-page-1/#comment-56371</link>
		<dc:creator>Tim Ferriss</dc:creator>
		<pubDate>Tue, 01 Dec 2009 03:37:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.fourhourworkweek.com/blog/?p=2202#comment-56371</guid>
		<description>Great comment.  I&#039;ll pass this on to them.  Thanks!

Tim</description>
		<content:encoded><![CDATA[<p>Great comment.  I&#8217;ll pass this on to them.  Thanks!</p>
<p>Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dustin Larimer</title>
		<link>http://www.fourhourworkweek.com/blog/2009/09/24/finally-the-end-of-food-journals-the-iphone-foodscanner-arrives/comment-page-1/#comment-56347</link>
		<dc:creator>Dustin Larimer</dc:creator>
		<pubDate>Mon, 30 Nov 2009 18:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.fourhourworkweek.com/blog/?p=2202#comment-56347</guid>
		<description>I picked up this app after reading this post.  I&#039;m a UX designer and have spent quite a bit of time designing and building iPhone apps.  The technology behind the scanner is great but unfortunately the project team forgot that humans will be using it.

I believe the app has potential, and I want to frame my critique as constructively as possible.

Data caching - don&#039;t make me wait for each day to load when skipping backward or forward.  This data should be cached - I mean we&#039;re only talking about formatted text and a reference ID.

Also, your users are humans - creatures of habit - and our diets reflect this.  If I have a carton of eggs in my fridge I&#039;m going to be manually searching (or skipping backward and reloading previous data) to add &#039;eggs&#039; every morning.  I found that about 75% of my entries were duplicates.  It would be great if these items were cached on the phone and offered with some sort of intelligent input method, like AutoComplete.  Again, we&#039;re only talking about some text and a reference ID.  The value offsets the storage use.

My last concern is that DailyBurn has another app in the store where I can see the results of my consumption and track workout/cardio activity.  I downloaded this app as well ONLY for the calorie-breakdown tracking so I can see the additive results of what I enter with the Food Scanner.  It would be really nice if the Food Scanner feature were just a paid upgrade from the initial app, or if the Food Scanner atleast reused the calorie-breakdown view.

I&#039;m not simply complaining about the design... These few simple issues are deal-breakers with regard to long-term adoption and continuance.</description>
		<content:encoded><![CDATA[<p>I picked up this app after reading this post.  I&#8217;m a UX designer and have spent quite a bit of time designing and building iPhone apps.  The technology behind the scanner is great but unfortunately the project team forgot that humans will be using it.</p>
<p>I believe the app has potential, and I want to frame my critique as constructively as possible.</p>
<p>Data caching &#8211; don&#8217;t make me wait for each day to load when skipping backward or forward.  This data should be cached &#8211; I mean we&#8217;re only talking about formatted text and a reference ID.</p>
<p>Also, your users are humans &#8211; creatures of habit &#8211; and our diets reflect this.  If I have a carton of eggs in my fridge I&#8217;m going to be manually searching (or skipping backward and reloading previous data) to add &#8216;eggs&#8217; every morning.  I found that about 75% of my entries were duplicates.  It would be great if these items were cached on the phone and offered with some sort of intelligent input method, like AutoComplete.  Again, we&#8217;re only talking about some text and a reference ID.  The value offsets the storage use.</p>
<p>My last concern is that DailyBurn has another app in the store where I can see the results of my consumption and track workout/cardio activity.  I downloaded this app as well ONLY for the calorie-breakdown tracking so I can see the additive results of what I enter with the Food Scanner.  It would be really nice if the Food Scanner feature were just a paid upgrade from the initial app, or if the Food Scanner atleast reused the calorie-breakdown view.</p>
<p>I&#8217;m not simply complaining about the design&#8230; These few simple issues are deal-breakers with regard to long-term adoption and continuance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
