Categories
Android News

More Complete Supported Android Devies List

The Delphi Wiki has a much more exhaustive Supported Android Devices list. It also includes the new Nexus 5 (running Kit Kat), Google Glass and Droid Razr M, to name a few. At the bottom of the list there are some BlackBerry devices listed too, all of which are either not tested, or not supported. Curious to see if any of those end up working

There is also a link to some easy to follow testing instructions if you want to test your own devices, including some scripts to help automate part of the process.

Looking at the list it is obvious that there are more supported devices than not. Most pass over 80% of the tests too, of course it is always nice to see specific devices verified.

5 replies on “More Complete Supported Android Devies List”

I need to warn you that users understand “Delphi Android support list” as a list of devices where Delphi applications only works.
This is really bad, because people points to that list, and says – well, I have device nnn, and it will not work with Delphi apps, since it is not in “delphi support list”.
This is real opinions from users.
And, since delphi apps works fine on my Sony Xperia V with Android 4.1.2, I don’t know how I can tell people about it, and why Sony devices not in the “support list”.

The better idea was to show list of devices, where Delphi apps will not work.

@Dmitry: It’s a wiki, why don’t you add your device to the “support list”

A negative list has the problem that a user might say… “This device is not on the list, why is your application not working?”. But it would be a good addition to the list, because it tells others that they don’t need to test a particular device anymore.

Would be nice to us outside US or without detailed knowledge about who is making what of each brands. Looking eg. for Galaxy, I findt that name is used by both Samsung and Google.

So please, ask people to specify what producer is involved for each telephone. Make it easier to look in shop to find what is needed to start developing for Android.

Personally I’m quite satisfied with using my Nokia Lumia 800 and still works ok, so no need to be exchanged by a more fancy model 🙂

@Dmitry Kuzmenko

Dmitry, people see what they want to see. If there isn’t a particular device in the list, it means this device was not tested. Who sees what:

Delphi pessimists: my specific device is not “compatible” with Delphi;
Delphi optimist: the device is not tested yet, but I believe can be tested ok right now or in the nearest future;

For Delphi-neutral people I can advice the following viewpoint (neutral, objective, real-life situation):
– there are three groups of devices:
– tested ok;
– tested with some limitation;
– not tested yet;
– not-tested devices means we are not certain about tests;
– some not-tested can be ok;
– some not-tested will be ok in the nearest releases/updates;
– tested devices with some deficiencies will be also fixed in the nearest releases/updates;
– problems in tests means Embarcadero DOES have knowledge regarding the devices and this is good too – understanding of a problem and reproduction of deficiency is step#1 in its solution.

Why this list is so important.
If we have no such list: people can only guess, what devices are ok. Not 100% probability means a great risk, especially for enterprises, when they plan to buy.
At the moment we do have list of 100% good devices. If I go buy an Android device I’ll say “thank you very much” many times, as I can see the list. The list is rather extensive, I mean not regarding all the Android devices available, but various price groups.

So, Dmitry, this is a task for Embarcadero guys and Embarcadero MVP to explain the other (especially, Delphi-pessimists) the meaning and the VALUE of this list.

As to my experience for Delphi XE5 seminars, after this explanation developers say “ok, great, now we understand the complexity of the problem and know the way how to have 100% device, at least, when planning the purchase for ourselves and our companies. Without such a list we won’t be so secure”.

Comments are closed.