?>
<?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: Flashy Restaurants	</title>
	<atom:link href="https://www.twofatbellies.com/2009/12/flashy-restaurants/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.twofatbellies.com/2009/12/flashy-restaurants/</link>
	<description>Living the delicious life</description>
	<lastBuildDate>Wed, 15 Sep 2010 16:27:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.8.9</generator>
	<item>
		<title>
		By: josh		</title>
		<link>https://www.twofatbellies.com/2009/12/flashy-restaurants/comment-page-1/#comment-82</link>

		<dc:creator><![CDATA[josh]]></dc:creator>
		<pubDate>Wed, 16 Dec 2009 01:51:12 +0000</pubDate>
		<guid isPermaLink="false">https://www.twofatbellies.com/?p=1909#comment-82</guid>

					<description><![CDATA[This is not just a mobile issue, its a functionality issue in general.  I have as much of a problem with the sites on my normal computer as I do on my mobile.  You all at Google may be working on mobile compatibility, but for these restaurants compatibility shouldn&#039;t be an issue at all.  The sites shouldn&#039;t be flashed-based to begin with, and then they&#039;d be mobile-compatible AND functional (read: easy to use) in my regular browser by default.  We at TFB are working around the clock to eat and write and we get peeved when it takes more than 10 minutes to go to a restaurant website to locate the menu just to recall the exact name of the dish we&#039;re currently writing about.]]></description>
			<content:encoded><![CDATA[<p>This is not just a mobile issue, its a functionality issue in general.  I have as much of a problem with the sites on my normal computer as I do on my mobile.  You all at Google may be working on mobile compatibility, but for these restaurants compatibility shouldn&#8217;t be an issue at all.  The sites shouldn&#8217;t be flashed-based to begin with, and then they&#8217;d be mobile-compatible AND functional (read: easy to use) in my regular browser by default.  We at TFB are working around the clock to eat and write and we get peeved when it takes more than 10 minutes to go to a restaurant website to locate the menu just to recall the exact name of the dish we&#8217;re currently writing about.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Claire		</title>
		<link>https://www.twofatbellies.com/2009/12/flashy-restaurants/comment-page-1/#comment-81</link>

		<dc:creator><![CDATA[Claire]]></dc:creator>
		<pubDate>Tue, 15 Dec 2009 23:56:57 +0000</pubDate>
		<guid isPermaLink="false">https://www.twofatbellies.com/?p=1909#comment-81</guid>

					<description><![CDATA[I don&#039;t think you&#039;re crazy, but I think the mobile phenomenon is a relatively recent one and website design is not a chef&#039;s area of expertise.  Google is working around the clock to try to make all of our apps compatible with mobile usage and we&#039;re still not perfect.  And we ARE supposed to be experts at web design. 

It will take time before brick and mortar businesses of all types understand that people&#039;s first impression of their store is most likely going to be online using a phone at a bar.]]></description>
			<content:encoded><![CDATA[<p>I don&#8217;t think you&#8217;re crazy, but I think the mobile phenomenon is a relatively recent one and website design is not a chef&#8217;s area of expertise.  Google is working around the clock to try to make all of our apps compatible with mobile usage and we&#8217;re still not perfect.  And we ARE supposed to be experts at web design. </p>
<p>It will take time before brick and mortar businesses of all types understand that people&#8217;s first impression of their store is most likely going to be online using a phone at a bar.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>