Why Google Needs Android to be Less Open

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
I think this is the first time I have ever heard someone call for Android to be "less open."

The "open" nature of the Android OS has contributed to its success, but the lack of control over the Android ecosystem as a whole creates a confusing landscape for app developers and could ultimately hinder the platform.
 
The fact that it's open and devices can be so different from each other is what led to it overtaking Apple in marketshare. Now that they have a large marketshare suddenly it's 'let's abandon open and diverse'? Basically all those that like tinkering with their phone's OS promoted Android, it grew in popularity from positive word of mouth, and now it's 'screw those tinkerers!'?
 
Although it would most likely slow down the adoption rate of Android by some manufacturers, I feel that in order to mature their operating system further, Google needs to step in and rewrite it's license agreement to include some type of restrictions on customizations and modifications to the core operating system components. Because the Android operating system is "free for all" environment, manufactures are highly modifying/customizing the core operating system components and releasing product into the environment that is not always compatible with others. Thus, developers are having to content with compatibility issues. Compatibility of applications should be primarily limited to system specifications (i.e. processor speed, RAM, etc.), not phone manufacturers.

Ideally, from a consumer standpoint, there should also be a clause to include a minimal amount of support and upgrades for Android enabled devices. Manufacturers are now releasing new phones faster than the operating system is progressing. That is fine, but they should be obligate to provide support for older phones for xxx amount out time or revisions.
 
Only developers care.

If the majority of devices that consumers have are android based, the developers will deal with it for the dollas.
 
It's not about being less or more open... it's about how strictly regulated the platform is.

Compare for example Linux and BSD. One is a thrown-together mixture of random bits and pieces, held together with liberal amounts of duct tape and gum. The other is a strictly-regulated, firmly led undertaking with a single codebase and strong focus. Yet the latter is the more open platform (BSD license).

I will continue to state that Android should have had a NetBSD foundation :)
 
The fact that it's open and devices can be so different from each other is what led to it overtaking Apple in marketshare. Now that they have a large marketshare suddenly it's 'let's abandon open and diverse'? Basically all those that like tinkering with their phone's OS promoted Android, it grew in popularity from positive word of mouth, and now it's 'screw those tinkerers!'?

I thought they over took apple because they had millions of phone models out there compared to only 1 iphone (well 2g, 3g, 3gs, 4g att, 4g vzw). There needs to be better statistics which track which models of android based phones are being bought. It grew in popularity because it provided a cheap alternative for cell phone makers to focus less on building their own software and more on hardware.
 
It would be nice if google would limit how much the carrier can butcher android.
 
There was a similar story the other day where it was stated that the carriers are going to start requiring locked bootloaders on Android phones. They're also working on the capability to remotely disable phones that are rooted.

We can thank all of the people that bought the DroidX's with their highly publicized locked bootloader for paving the way. :p


The open nature of the OS is the only reason I chose Android over the other smart phones. If they become locked down then I'll not be buying another one.
 
...................
Compare for example Linux and BSD. One is a thrown-together mixture of random bits and pieces, held together with liberal amounts of duct tape and gum. The other is a strictly-regulated, firmly led undertaking with a single codebase and strong focus................

I Like that saying!
 
I think that part of the potential problem is the same thing that happened to Windows Mobile. While most of that problem was simply neglect by Microsoft but another a big problem for Windows Mobile devices was simply the lack of controls, and tons of different devices with different screens and capabilities. So it's really more of an issue of asserting standards, not so much control.
 
The problem with the Android platform, is the cell phone creators themselves. Brand new phones are coming with outdated versions of Android. Already outdated cell phones are stuck with their version, cause cell phone makers aren't updating theirs.

This causes an array of problems for developers, and cell phone owners.

#1 If you aren't using Android 2.1 or higher, new applications won't work. Cell phone developers have to either ignore older Android phones, or try to make it backwards compatible, as best at they can.

#2 Froyo 2.2 or higher can store applications in SD cards, and even then only parts of the application. Older Android versions only allow applications to be stored in internal memory, which is usually very limited. This limits the amount of applications Android users can download.

#3 The best solution is to visit sites like www.xda-developers.com , which a lot of Android owners do. The problem is, now phones you thought that only had 1.6 or 1.5, now have 2.2 and 2.3 as well. Plus, very few people are doing this.

The obvious solution to this problem is to force phone manufacturers to use the latest Android OS, with every new phone. On top of that, force them to update their older phones. This is something you don't have a problem with on iPhones, where Apple updates even their old 2G and 3G phones with the latest iOS.

What does this mean? Your cell phone company is cheap as hell. Google could also work with the open source community, to get newer Android OS's ported to phones without the cell phone manufacturer. Course, there needs to be a way to do this without looking for a vulnerability on the Android OS.
 
I agree. It needs to stay open in the sense that I can install any app I want. On the other hand the OS itself needs to be standardized. Google needs to stop the companies like Motorola from butchering their interface.
 
I think the problem right now is the huge range of hardware and the capabilities each has with different version of android.

1) I still use the 1st android phone, and it does 95% of the newest android phones.... I still use stock android 1.6. Its totally capable of mods and running android 2.2 but the OTA updates from my phone company only went to 1.6 for my phone....

2) Now you have android 2.0 - 2.2 on the newest android phones coming out now.... these phones are a shitton faster than 1.5-1.6 android phones so they can run faster apps that older andoid phones cannot. This is the problem, as people make apps for the new phones, they do not care about the older users on android 1.6 anymore.... this is the ONLY problem with android.

3) Now you have the "tabletized" version of android a.ka android 3.0.... this is going to create even more apps that do not run on my older, 1st made, android phone using 1.6.

Again......... this is the ONLY problem with android but google has already realized it a few months ago if you read tech articles, so I see nothing but open sky for android from now on. I've been saying it since 2009, android is the best and will be #1..... looky that, 2 years later its true :D
 
IMHO the solution is Google to adopt a more rigid control over the "Android" trademark, conditioning the brand licensing to some kind of "compliance test". So any manufacturer can tinkerer and change the source code at will, but is prevented from using the "Android" brand if not compliant with Google rules.
Pretty much what Sun (and now Oracle) did with Java.
 
The problem with the Android platform, is the cell phone creators themselves. Brand new phones are coming with outdated versions of Android. Already outdated cell phones are stuck with their version, cause cell phone makers aren't updating theirs.

In essence what you're describing is the way Microsoft is handling Windows Phone 7, which was a big departure from Windows Mobile. I think Google in order to gain market share quickly wanted to make Android as easy and intimidating to carriers and phone makers as possible, now they'll probably have to go back and start tightening things up a bit now that market share isn't a problem.
 
This is not unexpected.

Google said in the past it wants Android to be modular in design. Many users hate the manufacturer themes thrown on top of vanilla Android. Sense, Blur, and TouchWiz in a word: SUCK. Now the real issue with them is they are baked into the Android code which in turn means longer development time for OS updates. Google wants these to be installed as add-ons that can be turned off or uninstalled so that upgrades can be carried out faster. There are easier ways to theme Android out there. T-Mobile, of all companies, released one on Github. CyanogenMod 7 incorporates this theme engine into its source code and other AOSP built ROM's are doing the same thing.

Google wants their users to have choice but not at the cost of fragmentation and slow updates.

No phone from HTC or Motorola (we won't even talk about Samsung) has received an update to Android 2.3 at this point. That source code hit AOSP back in mid-December 2010. If you want Android 2.3 you have two options: Nexus phone or Custom ROM. You realize that the CyanogenMod team had Android 2.3 nightly builds running on phones within 3 weeks of it hitting AOSP? Those builds were stable enough to be daily drivers. Here we are 4-5 months later and nothing from any major carrier. On top of that there is still the rumored 2.4 update to Gingerbread on the horizon. The question now is does 2.4 exist and if it does will it hit AOSP before 2.3 officially hits a phone like the Droid X or Droid Incredible?

That's why Google is trying to reign in things a little bit. This has nothing to do with wanting to create a walled garden like iOS. This will limit the amount of fragmentation which developers are complaining about. Odd they complain yet more developers are going Android then iOS at this point. http://www.droid-life.com/2011/04/0...ntation-86-of-developers-think-its-a-problem/
 
I think the problem right now is the huge range of hardware and the capabilities each has with different version of android.

1) I still use the 1st android phone, and it does 95% of the newest android phones.... I still use stock android 1.6. Its totally capable of mods and running android 2.2 but the OTA updates from my phone company only went to 1.6 for my phone....

2) Now you have android 2.0 - 2.2 on the newest android phones coming out now.... these phones are a shitton faster than 1.5-1.6 android phones so they can run faster apps that older andoid phones cannot. This is the problem, as people make apps for the new phones, they do not care about the older users on android 1.6 anymore.... this is the ONLY problem with android.

3) Now you have the "tabletized" version of android a.ka android 3.0.... this is going to create even more apps that do not run on my older, 1st made, android phone using 1.6.

Again......... this is the ONLY problem with android but google has already realized it a few months ago if you read tech articles, so I see nothing but open sky for android from now on. I've been saying it since 2009, android is the best and will be #1..... looky that, 2 years later its true :D
If you are still using the 1st Android phone, like I am, then it's the G1. The community at Xda-Developers have 2.2 and 2.3 working just fine, and 3.0 working but certainly not for daily use.

If you're a G1 owner, then please get Froyo by Laszlo. Root the phone. Update the phones radio using this . Give your SD card a ext4 partition or two, for installing applications onto your SD and swap file.

Anyone who's using an Android phone, and hates how it lacks features and updates, can find the same thing for their phones, at the XDA site.
 
Android already is less open. They won't release the source code for Honeycomb because *GASP* someone might actually use it.
 
This is not unexpected.

Google said in the past it wants Android to be modular in design. Many users hate the manufacturer themes thrown on top of vanilla Android. Sense, Blur, and TouchWiz in a word: SUCK. Now the real issue with them is they are baked into the Android code which in turn means longer development time for OS updates. Google wants these to be installed as add-ons that can be turned off or uninstalled so that upgrades can be carried out faster. There are easier ways to theme Android out there. T-Mobile, of all companies, released one on Github. CyanogenMod 7 incorporates this theme engine into its source code and other AOSP built ROM's are doing the same thing.

Google wants their users to have choice but not at the cost of fragmentation and slow updates.

No phone from HTC or Motorola (we won't even talk about Samsung) has received an update to Android 2.3 at this point. That source code hit AOSP back in mid-December 2010. If you want Android 2.3 you have two options: Nexus phone or Custom ROM. You realize that the CyanogenMod team had Android 2.3 nightly builds running on phones within 3 weeks of it hitting AOSP? Those builds were stable enough to be daily drivers. Here we are 4-5 months later and nothing from any major carrier. On top of that there is still the rumored 2.4 update to Gingerbread on the horizon. The question now is does 2.4 exist and if it does will it hit AOSP before 2.3 officially hits a phone like the Droid X or Droid Incredible?

That's why Google is trying to reign in things a little bit. This has nothing to do with wanting to create a walled garden like iOS. This will limit the amount of fragmentation which developers are complaining about. Odd they complain yet more developers are going Android then iOS at this point. http://www.droid-life.com/2011/04/0...ntation-86-of-developers-think-its-a-problem/

Excellent post and I 100% agree.

I for one really hope Google can rein in the poor standards put in place by the carriers/manufacturers. I really would prefer google to place tighter restrictions and only allow a vanilla OS to be used. Kinda lame you cannot update yourself or the forced apps that some carriers have installed, that you are not allowed to uninstall without rooting.
 
Tim Sweeney recently made similar comments about the difficulties of porting Unreal Engine games over to Android for this very reason.
 
Tim Sweeney recently made similar comments about the difficulties of porting Unreal Engine games over to Android for this very reason.

Actually his complaint was the bloatware installed so they couldn't guarantee enough free memory to run the application. However, many believe that to be nothing but a cop out because they are catching heat about not porting to Android. If an application needs more memory Android will close out idle apps. Android 2.3 is very good at that especially on older phones where RAM is limited (like the original Droid).

http://www.androidpolice.com/2011/0...ble-on-android-we-have-the-carriers-to-thank/
 
I think what google did to get android out there was a good short term plan but they are going to spend the next couple years cleaning up the mess it caused.

Manufacturers and carriers have too damn much freedom with them. They should have started out like iOS and WP7 keeping it locked down and consistent then adding the features and opening it up little by little. Now its a big clusterfuck that google is just now starting to try and fix.

But in the end what does google care? They just want them advertising dollars and they are getting that by putting android in the hands of everyone that can use a phone.
 
Back
Top