<?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: Yahoo mobile apps taken down, no one notices</title>
	<atom:link href="http://www.slashgear.com/yahoo-mobile-apps-taken-down-no-one-notices-27211113/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slashgear.com/yahoo-mobile-apps-taken-down-no-one-notices-27211113/</link>
	<description>Feeding Your Gadget and Tech Obsessions</description>
	<lastBuildDate>Thu, 17 May 2012 17:46:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: MobileGeorge</title>
		<link>http://www.slashgear.com/yahoo-mobile-apps-taken-down-no-one-notices-27211113/#comment-176856</link>
		<dc:creator>MobileGeorge</dc:creator>
		<pubDate>Sat, 28 Jan 2012 22:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=211113#comment-176856</guid>
		<description><![CDATA[Poor Yahoo. When the iPhone SDK was launched years ago, there were a number of people in the company who wanted to take Yahoo into the new smartphone app era, but instead people like Marcos Boerries were certain that feature phones were the future and crushed those efforts. Yahoo initially fought the idea of customized iPhone apps and instead produced apps that looked like their feature phone counterparts. Of course, these all looked and worked like crap and no one used them. As the smartphone was taking off, Yahoo continued to make significant bets on their old Yahoo Go and Blueprint strategies to support feature phones. When Bartz came in, she put an end to the feature phone focus but didn&#039;t come up with any new coherent mobile strategy. Individual product groups were left to come up with their own mobile ideas and so we got a mishmash of half-baked ideas released into the app store. Now, four years after the iPhone SDK ushered in the app era, Yahoo finally decides they need a better mobile strategy. Is it any wonder Yahoo is in the shape it&#039;s in?
]]></description>
		<content:encoded><![CDATA[<p>Poor Yahoo. When the iPhone SDK was launched years ago, there were a number of people in the company who wanted to take Yahoo into the new smartphone app era, but instead people like Marcos Boerries were certain that feature phones were the future and crushed those efforts. Yahoo initially fought the idea of customized iPhone apps and instead produced apps that looked like their feature phone counterparts. Of course, these all looked and worked like crap and no one used them. As the smartphone was taking off, Yahoo continued to make significant bets on their old Yahoo Go and Blueprint strategies to support feature phones. When Bartz came in, she put an end to the feature phone focus but didn&#8217;t come up with any new coherent mobile strategy. Individual product groups were left to come up with their own mobile ideas and so we got a mishmash of half-baked ideas released into the app store. Now, four years after the iPhone SDK ushered in the app era, Yahoo finally decides they need a better mobile strategy. Is it any wonder Yahoo is in the shape it&#8217;s in?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.slashgear.com/yahoo-mobile-apps-taken-down-no-one-notices-27211113/#comment-176813</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sat, 28 Jan 2012 16:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=211113#comment-176813</guid>
		<description><![CDATA[They removed Yahoo answers on Android. All that app was was a wrapper for the mobile site. Vsit the mobile site and you would get the same exact thing. ]]></description>
		<content:encoded><![CDATA[<p>They removed Yahoo answers on Android. All that app was was a wrapper for the mobile site. Vsit the mobile site and you would get the same exact thing. </p>
]]></content:encoded>
	</item>
</channel>
</rss>
