I think this touches on a much deeper issue of native vs web and frontend vs backend.
The first question I have is what percentage of people on mobile devices goto web vs native app? Then, when looking at web, it seems to me that frontend vs backend comes down to the preference of the site developers. My next question is why do frontend developers think backend device detection is so bad? Is it rational? Can we address it? Good or bad, media queries and fluid layouts seem to be the preferred frontend method. I personally feel the frontend approach comes with some complexity and some obvious performance hits. Better frameworks may or may not make this better. Given that the lifespan of any give frontend framework is now measured in months, this space is likely to remain ever changing. Also, given the nature of HTTP, there will always be a performance penalty in making requests before knowing your device context when ignoring the User-Agent. Backend approach via device detection and device templates seems like a practical approach. Adoption is low. My guess is that focus is moving toward frontend and lack of integration with popular web frameworks. I feel this space is becoming more stable since devices are more normalized (iphone, android, mobile browsers, etc), backend technology doesnt change as quickly, and projects like this exist. A good framework or backend alliance would go a long way. ________________________________ From: Werner Keil <[email protected]> To: [email protected] Cc: Andrew Savory <[email protected]> Sent: Friday, April 12, 2013 7:50 AM Subject: DeviceMap vs. Cordova Interesting, now it looks like meant to be useful client-side cross-scripting tools are about to be abused and tracked by popular Antivirus software: http://www.sophos.com/en-us/threat-center/threat-analyses/viruses-and-spyware/Andr~Cova-A.aspx The whole "Java on the Client used by Malware" outcry as opposed to "Java on the Server is Safe and the Foundation of Multi-Billion Dollar Businesses" does seem to apply to a Device Recognition on the Client using some sort of Scripting vs. Device Recognition on the Server using a Device Definition Repository choice, too. At least in some cases. Maybe it's time to shift priorities and resources poured into one side of this equation a bit? Especially on iOS while PhoneGap/Cordova seems to have been mostly accepted there, Adobe first and foremost will remember the ongoing security threats by client-side runtimes like Flash, Shockwave, ColdFusion and whatever else is or was out there... Android, too, with version 4 Flash was practically killed on Android recently. Could be, while true native apps won't die and in many cases are the best alternative, that companies and services who wish to address multiple platforms have to rethink portable apps over a security threat, this kind of Scripting always had an always will be, especially if more and more devices use such run-times A good reason not to let DeviceMap die, there seems to be demand and it may even grow in certain areas Regards, Werner
