Samsung could be a threat to Google

Today’s Monday Note by Jean Louis Gassée sparked an interesting thought and possibility that Samsung is gaining a serious upper hand in the Android world and could use it as leverage against Google. Now why would Samsung do that?

At this point, Samsung probably wouldn’t do anything to jeopardize the relationship with Google, after all, it’s selling tons of Android phones across the world and has become the number one smartphone maker on the planet because of it. Samsung owes a lot of that to Google.

On the other hand, it’s exactly this position that may allow Samsung to put pressure on Google. Samsung is large enough to dwarf its closest competitors and enough of an influence to pull off two of the three Nexus phones, the pinnacle and showcase of Android.

HTC and Motorola are the next largest Android manufacturers yet their sales are nowhere near Samsung’s and in fact have been cannibalized by its Korean competitor. The two companies are suffering.

Erik Sherman at CBS MoneyWatch puts Samsung’s share of Android phones at 55%. Given that it’s an estimation, it’s likely to be off by a bit but still an impressive ballpark figure. Since Samsung no longer officially announces its sales figures for mobile devices, it’s difficult to ascertain just how much of a lead precisely it has over its competitors both inside and outside of the Android ecosystem.

Android is still Samsung’s bread and butter as far as smartphones go, but it also has bada, its own mobile operating system and also Windows Phone to fall back on in case things go sour and you may never know what could happen in this industry. Look at Palm, Apple, RIM, Nokia. In the last five years, the mobile industry has changed so much.

Seeing what Amazon managed to do with Android along with a number of Chinese manufacturers, it’s not out of the question that Samsung could consider forking and maintaining its own version of Android away from Google, thereby creating its own ecosystem.

Why would it want to do that? Control. Google is beginning to assert a level of control that it previously did not require. Ice Cream Sandwich, the fourth iteration of Android, will require partners to include the default Holo theme as an option or risk losing Android Market access.

This may not sound like a big deal at first but it could ruffle some feathers at Samsung, HTC, and other Android companies. The very reason they came up with their own display themes is to differentiate themselves from the competitors and now Google wants conformity (albeit as an option) across the board and it is willing to punish partners for not abiding. After this, what else would Google do to assert control? That’s the question likely going around at the headquarters of those companies.

Google may not want to follow up further than this though, seeing that Microsoft hasn’t been successful going with this very strategy of requiring near-uniform features on its Windows Phone handhelds but it also has market challenges elsewhere. In fact, Microsoft is looking like it will rely mostly on Nokia to push its mobile platform ahead of its other partners.

However, if Samsung were to go by this route, it could face consumer backlash if it fails to execute it properly. An Android variant by Samsung would initially have to be compatible with Android Market apps, just like the Amazon’s Kindle Fire but it may decide to move its entire platform towards its own marketplace. It already has Samsung Apps as a repository for Samsung-exclusive apps and ChatOn could be step one towards establishing its own ecosystem.

At the moment, the smartphone market is run by four major operating systems; Symbian, Android, iOS, and BlackBerry. Windows Phone is still in its infancy and unlikely to make a significant enough move by itself in the next 12 months to break into the top 3. In three years though, who knows.

There’s no way Samsung would pull this off in the next 12 months but I’d be surprised if they’re not working on something that could significantly reduce their reliance on external parties.

Google looks like it needs to pull off its acquisition with Motorola Mobility more than most people think and somehow get people to buy Android phones from Motorola instead of others.

Google may be buying Motorola Mobility for its patent portfolio and is vowing to operate the company independently but down the road, it may be the most important play it makes for its Android platform if it can execute it well.

Fighting Content Piracy

From Jakarta Globe:

Business models should be based on customer demand and an understanding of what is technically feasible – not a desire to maintain existing models or cash flows. In other words, you need to adapt the map to the terrain – you cannot change the terrain to suit the map.

Fighting Content Piracy

Holo or Bust

Holo is the name of the new interface for Android, introduced in version 3 (Honeycomb) and refined in version 4 (Ice Cream Sandwich). Apparently Google wants this made widely available across every Android device running ICS because since debuting in 2008, the interface for Android devices had been a mixed bag.

Every manufacturer pushes its own look, its own style, over the stock Android interface. Motorola has its Motoblur skin, HTC had Sense UI, SonyEricsson has Timescape, Samsung with its TouchWiz and so on.

Naturally every Android partner wants to have its own signature look to differentiate itself from its competitors aside from hardware specifications, designs, and features. What this brings about however is inconsistency across brands, although for the majority of consumers it might not matter too much. After all, how many people go through multiple Android devices in such a short time right?

Developers however, has had to make sure their apps work across multiple devices with multiple interfaces. Most of the time, this isn’t an issue but apparently some apps can experience glitches due to conflicts with the added skin.

Up to this point, only the Google sanctioned Nexus devices offer the pure unadulterated Android experience and interface. Those seeking to have this have been made to seek out Nexus devices which may not necessarily be available in their respective markets.

Now, Google looks to be taking a stand and trying to force partners to make the stock interface available on every device and those who are not willing to comply will have access to Android Market revoked. Quite a stance from Mountain View.

That’s not to say manufacturers all must abandon their own themes. All their standard variants can still be the default but Holo must be made available and usable by consumers should they choose to use it. In other words, stock interface will no longer be the domain of Nexus devices, which is great news.

Holo or Bust

RIM to license BlackBerry to HTC, Samsung, others?

Seriously?

RIM to license BlackBerry to HTC, Samsung, others?

Lack of innovation adoption led to SOPA

The entertainment industry has always been about protecting its revenue, never about the consumers.

The introduction of new technology is always disruptive to existing markets, particularly to content/copyright owners whose sell through well-established distribution channels. The incumbents tend to have short-sighted goals and often fail to recognize that more money can be made on new platforms and new distribution channels.

Lack of innovation adoption led to SOPA

I guess this is today’s meme 

staff:

We’ll be rolling out Fan Mail — a new interblog messaging service — over the next few days for everyone.

You’ll be able to send Fan Mail from your Inbox, avatar menus, or with the icon in the top corner of the blogs you follow.

Have fun!

Google released its latest numbers on Android distribution earlier this week and the numbers aren’t necessarily surprising.

Over 96% of Android devices are on Gingerbread or older. With 54% of Android devices running Gingerbread v 2.3.3 or newer, it may sound like a good news for Google but as it turns out, more than 40% are still on Froyo, or 2.2, or older, something from at least two years ago.

Android developers will therefore need to target v. 2.1 as the base OS for apps if they want to reach the largest potential user base, or 2.2 if they’re willing to cut 8.5% of devices still running Eclair.

The release of 4.0 back in October (which is really version 3 as far as handsets are concerned) means nothing to the greater Android installed base as it has not been made available for any Android phone aside from Galaxy Nexus. If you happen to have an Android phone from 2010, you may as well forget about 4.0 for a while as barely any of them will get it.

Corollary to what was discussed in my post on DailySocial the other day, there is simply no incentive yet for developers to target the latest version for the next quarter as handset manufacturers won’t have them distributed to their phones until then. That makes it five to six months since 4.0 was released.

API level is essentially the level of technological advancements that come with each version of Android. Version 2.1 has API level 7 while version 4.0.3 is on 15. That should give you some idea as to the limitations that developers will need to work with if they decide to target the older version.

On the other hand, since most devices won’t get 4.0 for some time, and that the majority are on 2.3.x, developers would be working with only two or three API levels behind. After all, levels 11-13 are reserved for tablets running Honeycomb (3.x).

Speaking of Android tablets, they make up only 3.3% of the active installed base in the last two weeks.

The multitasking bar in iOS = browser history

Fraser Speirs:

you do not have to manage background tasks on iOS. The system handles almost every case for you and well written audio, GPS, VOIP, Newsstand and accessory apps will handle the rest.

There is almost absolutely zero need to manually kill the apps listed in iOS’s multitasking bar as it’s not a list of active apps but a list of recently used apps. It’s no different than if you had opened your browser and go to the history list. Apps listed there are not active. A few exceptions to this case of course exists such as when an app hangs but it doesn’t mean you have to clear the bar every time. It’s not like you clear your browser history regularly do you? 

The blog post is not a particularly long one, but for the short-attention span crowd, go straight to the summary section.

Even the Geniuses at Apple’s Genius Bars still get this wrong.

The multitasking bar in iOS = browser history

Microsoft bids farewell to IE 6

Even its creator can’t wait until it goes away completely. If you’re still using IE 6 (or even IE5 -shudder) time to take a look at your browser policy and follow the lead. The world has moved on to far better things, if you haven’t, what’s taking you so long?

So as we kick off 2012, we call on the rest of the world – make it your new year’s resolution to end IE6

Microsoft bids farewell to IE 6