/bow
They don't, of course. They grow tired being handcuffed by google. They believe they can be very profitable by eliminating Googles restrictions and using their own software.RobertR said:I'm trying to figure out why a company would get "tired" of being "very profitable".
A windows phone doesn't make sense either, since that's replacing one set of handcuffs for another.We've got Nokia, ironically, trying an Android phone not tied to Google services.http://www.theverge.com/2014/2/25/5445150/why-is-nokia-making-android-phones"The X series is simply a test of that strategy right now, a method for Nokia to gauge whether developers will truly port their apps across and build momentum. Windows Phone app growth must have been frustratingly slow for Nokia, and the platform lacked the low-end reach that Nokia had enjoyed with Symbian. It’s also a way for Nokia — and Microsoft in future — to try to disrupt Google’s use of Android the same way Amazon had with the Kindle Fire series. There are no Google services on these phones, and Android app developers who want to build for the X will need to edit the in-app payments, location, and notifications aspects of their apps. This gives Nokia and Microsoft control of the all important in-app purchases transactions, mapping data, and both push notifications and messages."And there's the story that Google is requiring Samsung to hew closer to Googles vision of Android. http://www.pcmag.com/article2/0,2817,2430151,00.asp"Multiple sources familiar with the companies’ thinking say the two technology giants began hammering out a series of broad agreements at CES that would bring Samsung’s view of Android in line with Google’s own. The results of the talks, which have only just begun dribbling out to the public, also underscore the extent to which Google is exerting more of its influence to control its destiny in the Android open source world."And then there's this Samsung story about Tizen. And the story is that it's too boring to comment on, because it's basically a perfectly mature Android version, sans Googles ecosystem.http://arstechnica.com/gadgets/2014/02/hands-on-with-samsungs-tizen-os-a-impressively-capable-android-clone/"The OS runs on "prototype" hardware that very closely resembles a Galaxy S4. Tizen is a Linux-based OS primarily developed by Samsung, and, the theory goes, Samsung's grand plot is to eventually turn Tizen into a drop-in Android replacement, own the market with an OS of its own making, and never have to deal with Google again. So far, Tizen seems a pretty accurate Android clone, but it's shocking how far along it is. On the surface, it seemed just as capable as a TouchWiz Android device. Samsung has done such a good job of replicating the Android interface that there is very little to write about—everything looks and works similarly to the way it does on Android, just without any kind of ecosystem."My first reading of the world was wrong. I thought Google would grow tired of being the free, generic os maker while Samsung made all the money from their phones. But more than that is going on. Google is closing up its OS, and becoming a more proprietary OS. It's pushing OEMs to hew closer to its vision, and particularly it's services to extract the revenue from its free software. Samsung, perhaps, wants to control its own destiny and not be turned into a generic phone OEM for Google.Hanson said:It would be seismic, because it would mean hell just froze over. It's not going to happen because Samsung doesn't have the app ecosystem necessary to support a successful OS. And because of the Handset Alliance, Samsung would not be able to release a Tizen phone that would run Android apps (it's the same reason Acer couldn't release an Aliyun phone). If Samsung really wanted to test the waters to see if they could make it without Android, they should release a Windows phone and see how the market reacts. While Samsung is popular because they have the feature sets people want, the core of the experience is Android. As the article points out, no Google services means no sale, even if you could sideload Android apps.
Presumably it would be a drop-in replacement. Most Android apps would work as-is. Specific cases would have to be recompiled against Samsung's variant. Games might need the most adjustments. Here are two articles discussing pros and cons of MS forking android for its own good, which I think is equivalent. Ars Technica says it's untenable. http://arstechnica.com/information-technology/2014/02/neither-microsoft-nokia-nor-anyone-else-should-fork-android-its-unforkable/Stratechery claims Ars overstates the negatives and it's quite doable:http://stratechery.com/2014/microsofts-mobile-muddle/I'm not knowledgable to judge the merits, but I'm intrigued by the proposition it can be done:"(I am aware of Peter Bright’s article that says Android is unforkable; I find it technically accurate but misleading. Of course there are some APIs in GMS, but a tiny amount relative to AOSP, and almost all related to cloud services which Microsoft by definition wants to replace. Bright waves this away by saying it’s “too much work,” but it’s much more work trying to get developers to build entirely new apps than it is to get them to change a few lines of code to support your store. Sure, Google might try to mess things up, but far better to rely on your own ability to adjust than on developers over whom you have no leverage.)"Let's suppose it's doable, but would cause short term pain. Why would Samsung do it! Long-term freedom and long-term success. They don't want to be Dell to Google's Microsoft: top OEM for 30 years, but ultimately destroyed by MS playing the hardware vendors against each other to maximize its own profits.RobertR said:That's why I asked the question why Samsung would abandon a situation that's making huge amounts of money for them. "It's just like Android, but it's not tied to Google and has no ecosystem". How is that a selling point?
Ironic that you would talk about a system requiring "adjustments" to apps in a thread titled "the downside to fragmentation". Still can't see how consumers benefit from this.DaveF said:Presumably it would be a drop-in replacement. Most Android apps would work as-is. Specific cases would have to be recompiled against Samsung's variant. Games might need the most adjustments.
You are thinking too short term tho. IF such a fork were to occur and Samsung gets their own app store and creates their own front ends to google services they then have a platform where they control the fragmentation, same as Apple (and Amazon) which Google and to a lesser degree Microsoft cannot.You can argue if that is better or not for the over all marketplace of consumers (I'd expect it wouldnt be, but too early to tell) but for those consumers who choose that new samsung platform clearly having a homogenous ecosystem has its benefits and fans (like me!).RobertR said:Ironic that you would talk about a system requiring "adjustments" to apps in a thread titled "the downside to fragmentation". Still can't see how consumers benefit from this.
Why would developers want to create apps for a separate ecosystem that's "just like Android" (except for all those modifications, of course) when the Google play store is already in existence? What's the sales pitch to consumers? "It's just like Google, but it's not"? Maybe it appeals to you for being the (kinda, sorta) unAndroid, but I don't see why many people would flock to something that "is and isn't Android".Sam Posten said:IF such a fork were to occur and Samsung gets their own app store and creates their own front ends to google services they then have a platform where they control the fragmentation, same as Apple (and Amazon) which Google and to a lesser degree Microsoft cannot.You can argue if that is better or not for the over all marketplace of consumers (I'd expect it wouldnt be, but too early to tell) but for those consumers who choose that new samsung platform clearly having a homogenous ecosystem has its benefits and fans (like me!).