Android developers are obviously excited about the new 1.5 version of the SDK. The so-called “Cupcake” update features several new features and overall improvements. But, “don’t get too excited yet,” a post on the Android developers blog reads today. Apparently, the new release is going to break a number of current apps.
And these aren’t just random apps. Google said it has extensively tested some of the most popular apps in the Android Market, and found that many were broken due to “bad techniques.” As such, it created a list of five things to avoid when building your app — and suggests that anyone who developed an app using Android 1.0 or 1.1 pay attention.
The list is pretty straightforward. Google says you shouldn’t use Internal APIs, and shouldn’t go overboard with layouts. But one of the more interesting ones is “Bad Hardware Assumptions.” This notes that developers should not build for the Android assuming the hardware its running on has certain specs. The example they use is the physical keyboard, which the G1 has, but other upcoming Android phones — like the HTC Magic (aka the G2) — will not.
This speaks to a problem the Android platform presents developers, that the iPhone does not. While it’s great that Google has opened up Android and wants it to be on as many devices as possible, that also means that developers will need to develop programs that can be used on many devices. iPhone developers, on the other hand, know exactly what they’re developing for, as there is only one device (well okay, two with the iPod touch, but it has the same basic specs) that it will run on.
Here’s the 5 techniques Google says Android developers should avoid:
- Using Internal APIs
- Directly Manipulating Settings
- Going Overboard with Layouts
- Bad Hardware Assumptions
- Incautious Rotations
fp
I never understood this, who gives a shit…
How awesome! You totally got second post!
I know you’re getting paid in ice cream. However, your name remains on Venturebeat’s masthead.
Is that some sort of punishment….
…for Venturebeat, of course?
This is why android will never reach the popularity of the iphone. This kind of fragmentation gives developers migraines and makes development costs soar.
As I developer I for one hope android dies. I love having just 1 device to worry bout. Write once, test once and have it work on 30+ mil devices.
Nothing beats that.
The idea of one OS is a great idea. While we’re at it, lets take away any options for customization. After all, the purpose of any OS is to make life easier on developers.
That is absolutely ridiculous. The variety of device availability is why the Android *will* exceed the popularity of the iPhone, in due time of course. People will have the ability to make the choice as to what form factor they prefer instead of having that decision made for them by someone else.
Any developer aiming to develop an application to be used on a large scale should have the basic common sense to not make assumptions about the hardware capabilities of devices.
According to that logic, the Macintosh should be *far* more popular than Windows-based PCs. After all, the hardware is much more consistent, whereas when you write for Windows, you never know what the hardware is going to be.
Excellent point, couldn’t have said it any better myself.
I’m actually surprised by the whining from developers that prefer the iPhone. You guys are missing the big picture. Apps created for Android should allow developers to make a lot more revenue than apps created for the iPhone. That is, if you consider that the developer’s Android app will be on more than just one phone, unlike apps created for the iPhone.
I don’t get the Alan Tudyk picture reference. Please explain!
Here’s all you need
Is there a list out there detailing which Apps will be broken? I’m sure Cupcake will be amazing when it hits and do a lot of good, but if it kills Apps that I actually paid for, I’ll be pretty unhappy.
I like vanilla cupcakes with chocolate frosting, and sprinkles.
apple vs. google… the match begins.
gasp
marvin
http://yousuggest.us
Not worried about broken apps. Anything that doesn’t work will be quickly discarded and replaced with an update or 3 competing apps that do the same thing. There’s something mystical and just about Android market’s survival of the fittest approach.
Dear TC,
Your server is jacked up. On another note, I didn’t realize you used Nginx. +1.
Google and apple can both be winners in the smart phone market. Stock market keeps surging http://iamned.com/blog/ recession is over
This is the problem with “open source”; it invites people with various levels of coding skill in on the party, some with more skill than others.
I agree. Every one of the apps in the iPhone store are of the highest quality.
What part of android being open source means lower skill developers can develop on it? If anything, the language for the iphone is “easier” which means worse developers will be there.
The mentality difference here is clear. If you believe in capitalism and the free market pruning out the people who don’t serve their customers you understand android. If you want to force everyone to use a specific set of rules controlled by one overseeing company you get offended when people with adventure and the american spirit step out.
There is one ipod touch in my house because it fits our need and 1 android device and 2 windows mobile devices because they fit the others needs. THAT is what it is about
Tighter!
MG: thanks for the update (again). You seem to be attracting quite a crowd of well wishers and social gadflys. Very funny. Well that means you are getting to be important.
http://www.agor...m/products.html
Pffft!
Blackberry and WM developers have been dealing with this from day one. No big deal.
While the iPhone has a significant advantage in install base and developer mindshare, I wonder how long they’ll retain this “simplicity” advantage, especially in light of their June iPod/iPhone announcement.
It’s been two years since the iPhone was released without an appreciable boost in speed. Apple’s still got the edge in software quality, but Google and Palm are closing it. I say they’re going to release a more powerful phone (for video capability at the very least) so that they can once again open up their perceived technological lead. And *poof* there goes the simplicity advantage.
LOL Pictures speak a thousand words, tighter!
T-mobile’s moved a million G1s now so they might have to ‘tighten’ the guidelines.
ha
It is really a great idea. While we’re at it, lets take away any options for customization. After all, the purpose of any OS is to make life easier on developers.
I’m the only one in this world. Can please someone join me in this life? Or maybe death…
It’ll be interesting to see what happens when the new Android devices running VGA and QVGA screens start to arrive.
The O/S may have been designed to support different resolutions, but my gut feeling is that everyone has been working to HVGA – which will start to cause lots of problems.
Hasn’t anyone ever heard of windows mobile running on different hardware specs before? If windows mobile didn’t do as well, it is not because of this “disadvantage”, but rather the lack of innovation. Android should not have this problem.
Thanks for breaking my phone. Next time learn to code befor you push an update that breaks every single one of my apps.
I’m so sick of these lame f-tard googlers.