Android Compatibility and Fragmentation

tbray writes "Here are the details on the Android Compatibility Program — which combines the source, a formal compatibility spec, an open-source test suite, and access to the Android Market as reward for good behavior (program page). People like to rant about the subject of fragmentation, so here's TFM that they should be R'ing first."

Comments

hrmf...

[hitmark]

this should have been made perfectly clear from google's side from day one. Yet everyone kept talking about android marketplace as if it was a part of the android source until the first android based devices without marketplace showed up, and none could figure out why.

i only ran into it after ranting about google's mismanagement of marketplace access on some forum, and got a link handed to me.

another issue is that 1.6 required that a compatible device could function as a phone. So any device thats been in development since 1.6 was first released, wont have marketplace unless its a phone or stalls its release until they can get 2.1 or newer working and approved by google. And even then the max resolution of the screen is 800x600, and i think the screen size is in the 5-7" range.

basically, google is lagging badly behind where third parties want to go with android. And its not helping that marketplace is only really usable in select nations so far (and when a sim is inserted into the device).

Re:This doesn't solve fragmentation

[ergo98]

The problem is (from an app developer standpoint) is that there are too many variables in the android world to code an app once to run successfully across the ecosystem.

Yet strangely many people are successfully doing this.

You have to design a version for on-screen keyboards (because it'll use part of the screen real estate) separately from a version that uses a hardware keyboard. They don't need to be separate apps, but you need to design (visually at least) for both scenarios, or you end up locking out a good portion of the people who use android devices.

Completely wrong. Where are you getting this from?

Sure, there are 100,000+ android devices out there

Over 100,000 Android devices activated per day.

so in order to sell your app on all 100,000 of those phones you've got to tweak your app for each device

No you don't. You have no idea what you're talking about. And you're at Score:4 right now, which is shameful.

One way to call the Camera API

Ugh. You shouldn't have posted because almost everything you have said is just completely wrong.

The Android developer platform is extraordinarily universal. There's a density independent pixel format (which is how an app looks almost the same on a 320x480 screen as it looks on a 480x800 screen), support for varying screen ratios, a single way to inter-operate with the camera and send emails and read the GPS signal and get orientation signals, or even do advance OpenGL graphics.

One app to rule them all.

There are of course differences and occasionally "quirks". If you make a rich graphics game it's going to run terribly on a G1. Flash is only available on some devices. And of course if you have to target a newer API, presumably because it has a feature that you can't live without, you limit your app to that version and above (just as if I use Transactional Filesystem calls my Windows app would be Vista or newer).