EVE Technology Lab

Which version of Android are you using? 2.x, 3.x or 4.x?

Can we get a survey on this? Specifically for Eve users here :) I know what the google chart says but it says nothing about here :)

2.3.5 here

2.3.5 with an update to ICS expected in summer.

4 ICS on Asus and 3.x on HTC Phone

2.3.7 (CM7 http://www.cyanogenmod.com/)

Maybe CCP can add a REST API that we can register our client platform versions then publish a pie chart?

That would be useful to the community especially if CCP think for a minute they can cream us for license fees WHICH WE CAN AVOID LEGALLY (but that is another thread discussion) :) , hint: ccp hint :) If CCP want to charge us, they can at least give us app builders some assistance with metrics and data of the users we are targeting. Valve do it for the entire industry, why cant CCP do it for their customer base? Such a small thing goes a long way.

Please?

take a look on the android website it gives you a nice pie chart of what versions are in use.

I don't need any license from CCP to build around their API as long as I don't touch their protected works, I only need to license it if I am redistributing their protected works so there as far as I am concerned, that is not an issue from this point on especially since the recent EU ruling on API's not being protected. Using any of their protected works just sets me up regardless of their ever changing license terms (which they would change over time) and would have to be reagreed on each change and every sub-clause severed if it is in breach of local laws but ofcourse their license will be under Icelandic law which will also be aligned with EU laws but there will be regional variation then again protected works are pretty much covered by international agreements, except API's under EU law and also reverse engineering also under EU law to help interoperability with systems.

This is something CCP should provide as Google do it for the entire API levels, it would be a good thing for all Eve 3rd party app developers to have some real world metrics on which platforms players are using. It would be a simple thing to add to the existing planned CREST API to collect some metrics. Sure 100 app developers can build their own metrics collection in all their apps, but then you would all cry that we are SPYING on you via our apps and label it spyware, it would be better if this is collected by CCP and give this out as a developer assistance program.

There is a reason they are not charging for their developer license, because they 1) cannot enforce it if all we use is their API and do not touch their protected works and 2) it would kill app development and leave it only for the big boys like battlespastic site

Anyway, please don't derail the thread, please continue to post your Android versions, it is helpful to get an indicator on what API levels we can target which pretty much looks like API level 8 and the compatibility packages are not fully implemented on all features (PreferencesFragment for one) and anyway, who wants to build NEW apps around a "legacy" library, given that over the next 6 to 12 months 2.x will be history and 3.x will be the minimum bar, we are already hitting API level 15 (4.0.3+), major redesign came in 3.0, 2.3 is dead and buggy as hell on HTC (especially bluetooth pairing/connection stalling issues). So these metrics do help very much on what to target.

Thanks, I pretty much see it's API 8 and compatibility libs, the apps I have in mind will be hooking into Bluetooth and on HTC, API 7 and 8 is VERY VERY buggy (bluetooth stack stalling and it just dies) unfortunately and HTC is a popular make, I am hoping to jump to 3.0 and up as API level 11 overtakes 8 in the next 6 to 12 months and ditch the compatibility library.

Nice product advertisement btw lol sneaky lol

I know lol but the HTC bluetooth stack stalling is a major problem I don't want, I am using it right now and we had to just cut 2.x out altogether due to the bluetooth issue on them. Cannot sell a product that is intermittently not working to our customers lol.

I am thinking of going 4.x only and adding tablet specific support and a lighter front end for mobile devices.

The Bluetooth issue is a deal breaker for my product though. I don't want HTC headaches. Frankly, from my experience in them, AVOID HTC; and buy Motorola and Samsung , in fact anything but HTC, at least they seem to test their stuff and it just works. HTC vendor specific alterations to the stock droid platform are the major HTC defects. Currently we don't support those devices, period. it was that much of a problem.