<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Fragmentación on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/fragmentaci%C3%B3n/</link><description>Recent content in Fragmentación on Karpoke - Just Another Blog</description><generator>Hugo -- 0.159.0</generator><language>es</language><lastBuildDate>Sun, 14 Sep 2014 16:41:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/fragmentaci%C3%B3n/index.xml" rel="self" type="application/rss+xml"/><item><title>Google’s Got an Open Source Android Problem</title><link>http://karpoke.ignaciocano.com/2014/09/14/googles-got-an-open-source-android-problem/</link><pubDate>Sun, 14 Sep 2014 16:41:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2014/09/14/googles-got-an-open-source-android-problem/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Never has a tweet been more true, or potentially more disastrous for a
vendor. Years ago Google’s Andy Rubin, stung by Steve Jobs’ criticism that
Android wasn’t truly open, tweeted that anyone could fork - i.e., modify -
Android, making it ”open” in the truest sense of the word. Unfortunately for
Google, many OEMs took Rubin at his word. Today, Google’s Android business is
booming, but it’s clear that Android fragmentation minimizes just how much
Google—or its ecosystem of app developers—can make from the open-source
mobile OS. Unfortunately, according to new ABI Research data, it’s only going
to get worse.&lt;/p&gt;</description></item></channel></rss>