Difference API / TeraWurfl Explorer

[elopez]

Hi,

We are currently testing .NET API before purchasing a license,

If we use this UA with the API :
LG-GD510-Bouygues/V100 Teleca/WAP2.0 Profile/MIDP-2.1 Configuration/CLDC-1.1
we get a "generic" response
but if we use tera-wurfl explorer (http://www.tera-wurfl.com/explore/index.php)
then we get the mobile LG GD510

Why can't the API return the same response ?

Thanks by advance,

Eric.

[kamermans]

The difference is caused by a difference in logic between the DB API / Tera-WURFL and the original WURFL APIs (PHP, Java, .NET). Since Tera-WURFL was developed seperately from the official APIs, sometimes different results are obtained. We are working hard to bring the best logic of all APIs together and apply it to all the APIs so the matching is identical. You can confidently purchase the .NET API and know that it will be matching the same as the other APIs in the near future. It should also be noted that the .NET is not "worse" at matching, it's just different. There are cases where it will match more accurately than the DB API as well.

[elopez]

Thanks for your quick answer.

The thing is, even if the .NET API is not worse as you say, during our test the web interface gave better results than the .NET API.
We are really interested in the .NET API but if we have to wait several months, we will have to study other solutions. Unfortunately, as the API is really easy to use.

So what do you call a near future ? Can you give us a date ?

Regards,

Eric.

[sm_support2]

Order of one month from now.

Can you hold your breath until then?

[kamermans]

Indeed. For what it's worth, I am the author of the DB API (Tera-WURFL) and I created the site you're referencing. In ScientiaMobile I am the COO, so I can tell you with great certainty that all the APIs will be updated very soon to include the new, more accurate matching strategies. You will definitely see incremental updates that bring the matching algorithms closer together in the coming weeks. In the meantime, you may be interested to know that the WURFL Cloud product (currently in Beta) uses the same matching logic as the DB API and it includes a .NET client. Feel free to try it out!

[elopez]

Thank you for your answers !

[nickspoon]

I realise that this is an old thread, but there are still some differences between the various APIs.

I have 2 UserAgents for the Samsung Galaxy SII, after it has been upgraded to Android 4.0.4, one for the default browser and one using the Chrome (Beta) browser. On tools.scientiamobile.com these are both recognised, and have resolution_width 480:

Default: http://tools.scientiamobile.com/?user-a ... ari/534.30
Chrome: http://tools.scientiamobile.com/?user-a ... ari/535.19

However, using the Database API v1.4 (http://www.tera-wurfl.com/explore/index.php) and the .NET API v1.4 and v1.4.1 with the latest commercial data snapshot, only the default browser version is recognised, and the Chrome version returns "Generic Android 4.0", with resolution_width 320.

So what API does tools.scientiamobile.com use, to get better results than the Database API and the .NET API? Can we expect these descrepancies to continue, or are the different APIs still converging on the same logic?

[kamermans]

The tools.scientiamobile.com website uses the development snapshot of the Database API with the latest commercial data snapshot, and, while some devices are detected more accurately, it's also possible that some may be detected less accurately since the development branch is not thoroughly tested for regression until it is released.

In the case of Chrome beta on Android, there is a fix in the development branch that specifically improves detection. The problem is due to Chrome changing the mobile keyword from "CrMo" (Chrome Mobile) to "Chrome" a few weeks ago. The new version will be available in the near-future, and you are welcome to send us an email or private message and we can send you the latest development version of the code for your testing.

[nickspoon]

OK, thanks for that Steve. I'm happy to wait for the next production version of the API.

Does this mean that the different APIs (Database, PHP, .NET etc.) all have the same logic now?

[kamermans]

For all practical purposes the logic between the APIs is the same, however, there still may be subtle differences. We test all the APIs against each other to ensure the behavior is as close as possible.