Comments on: Device Adaptation Makes Sites Less Transparent http://www.thisismobility.com/blog/2006/05/26/device-adaptation-makes-sites-less-transparent/ Ripping mobility from the clutches of telecom Thu, 29 Dec 2011 20:46:11 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Prashant http://www.thisismobility.com/blog/2006/05/26/device-adaptation-makes-sites-less-transparent/comment-page-1/#comment-7149 Prashant Thu, 08 Jun 2006 13:06:31 +0000 http://www.thisismobility.com/blog/?p=125#comment-7149 Hi Mike you have touched my pain point here . i agree to you on the point that it will be good for the mobile dev community if we shift the action to Device Side and avoid using the Server Side Logic . but i am not sure if that is a good idea for End user . as a mobile we b developr i would like to do what you have suggested but not at the cost of End User . with the rampant fragmentation in mobile device market its unlikely that we will reach a common platform soon and AppLayer based devlpoment which is oblivious to device undernith is a far cry . crux of the problem is that Mobile OEM are unwilling to learn from History PC Market and lesson in "benifits of Standarization " it offers . on a second thought they might know the advantage of a uniform standards but No body wants to end up being the next IBM in this process . Hi Mike

you have touched my pain point here . i agree to you on the point that it will be good for the mobile dev community if we shift the action to Device Side and avoid using the Server Side Logic . but i am not sure if that is a good idea for End user . as a mobile we b developr i would like to do what you have suggested but not at the cost of End User .

with the rampant fragmentation in mobile device market its unlikely that we will reach a common platform soon and AppLayer based devlpoment which is oblivious to device undernith is a far cry .

crux of the problem is that Mobile OEM are unwilling to learn from History PC Market and lesson in “benifits of Standarization ” it offers . on a second thought they might know the advantage of a uniform standards but No body wants to end up being the next IBM in this process .

]]> By: miker http://www.thisismobility.com/blog/2006/05/26/device-adaptation-makes-sites-less-transparent/comment-page-1/#comment-5879 miker Sun, 28 May 2006 07:57:14 +0000 http://www.thisismobility.com/blog/?p=125#comment-5879 I agree that it's not a problem for the user directly, but I do think that it causes undesired side-effects in terms of the overall community of potential producers of content for mobile devices. I agree with the end goal of mobile devices participating in the CSS/JS/XSLT way, but I wonder if there's a way to make the currently hidden parts of device transformation more visible? Kind of like what WURFL did for device capability. Instead of everyone embedding their own checks for what devices can do, coded up according to their own understanding of how to test for those features, there's a common layer that embeds all that know how in a reusable config file and set of components. Think about the question from the point of view of a person who has some information they would like to make available to folks on mobile devices - but who isn't a mobile professional and doesn't really want to be one. What can be done to aid that person in putting together their application in a way that it works on as many devices as possible without requiring them to learn the ins and outs of how different devices work and what needs to be done to handle them? - Mike I agree that it’s not a problem for the user directly, but I do think that it causes undesired side-effects in terms of the overall community of potential producers of content for mobile devices. I agree with the end goal of mobile devices participating in the CSS/JS/XSLT way, but I wonder if there’s a way to make the currently hidden parts of device transformation more visible?

Kind of like what WURFL did for device capability. Instead of everyone embedding their own checks for what devices can do, coded up according to their own understanding of how to test for those features, there’s a common layer that embeds all that know how in a reusable config file and set of components.

Think about the question from the point of view of a person who has some information they would like to make available to folks on mobile devices – but who isn’t a mobile professional and doesn’t really want to be one. What can be done to aid that person in putting together their application in a way that it works on as many devices as possible without requiring them to learn the ins and outs of how different devices work and what needs to be done to handle them?

- Mike

]]> By: C. Enrique Ortiz http://www.thisismobility.com/blog/2006/05/26/device-adaptation-makes-sites-less-transparent/comment-page-1/#comment-5878 C. Enrique Ortiz Sun, 28 May 2006 05:47:23 +0000 http://www.thisismobility.com/blog/?p=125#comment-5878 transparency is a relative thing... from the end-user's perspective, device transformation is a good thing (and pretty transparent) - the web site is properly formated based on user-agent (and/or any other attribute). device adaptation, and related server-side "magic" is not problem in my opinion... one day (hopefully sooner rather than later) we get to have consistent behavior (from CSS to JS to XSLT) across mobile browsers, then transformation will be able to happen totally on the client side, and *that* source will be able to be viewed and shared. ceo transparency is a relative thing… from the end-user’s perspective, device transformation is a good thing (and pretty transparent) – the web site is properly formated based on user-agent (and/or any other attribute).

device adaptation, and related server-side “magic” is not problem in my opinion…

one day (hopefully sooner rather than later) we get to have consistent behavior (from CSS to JS to XSLT) across mobile browsers, then transformation will be able to happen totally on the client side, and *that* source will be able to be viewed and shared.

ceo

]]>