Thursday, May 7, 2015
Wednesday, June 12, 2013
Mobile Devices have become Ubiquitous, and a Complex Mobile Ecosystem
This ecosystem now consists of mobile content providers, mobile enablers, and infrastructure providers such as aggregators in addition to the network providers and device manufacturers that have existed since day one. The goal of the evolution of mobile has been to bridge the gap between mobile and desktop to deliver an optimum experience to users on their mobile devices.
What makes mobile content different from web-to-desktop content?
As will be described in detail below, mobile content is different in many ways from Web-to-desktop content. The mobile world is fragmented - there are thousands of mobile device models, with different form factors, operating systems, and browsers. On the Web this is not an issue. This means that even though similar technologies are generally used to build Websites for mobile devices and desktops and even though in some cases the same web server might also be used to send content to both, multiple versions of the mobile content need to be created, stored, and delivered.
In addition, website content is downloaded very differently to a mobile device than to a desktop browser in order to provide the desired end user experience.
Web Content on a Mobile Device.
The mobile device connects to the operator network.
Every mobile request goes through the operator's backbone.
Content server sends different content depending on device capability.
Web Content on a Desktop.
Desktop connects to the ISP.
ISP routes through the Internet to download content.
Content server sends same content for every request.
Device-specific mobile content-a monitoring challenge.
One of the most important differences between mobile and desktop-based web content is the need for mobile content to be tailored for the various characteristics and capabilities of a particular device. This added level of complexity affects development of monitoring strategies, and it must be taken seriously in order to truly understand how the full spectrum of end users accessing mobile content will experience it. Clearly this expansion of the scope of content monitoring is one of the major differentiators from a desktop-based web monitoring strategy. With literally hundreds of device types in circulation and more coming on the market each day, attempting to understand the end-user experience by manually testing content on each device is cost-and time-prohibitive; automated monitoring strategies are required.
What is the impact on performance monitoring?
In the web world, both the user interface and the delivery mechanism have been standardized for years.
However, mobile content must be routed to the user through an operator network, and additional operator.
Specific content may be added during the download. Also, different devices render content differently, so when the Web server detects a specific device type it may choose to send a variant of the generic content to the requesting device. Finally, different devices are capable of handling the various components of a download differently (for example, images, text, and third-party content) - which can dramatically vary download time.
This means that web performance-monitoring techniques that work with desktop-based web content will necessarily fall short in a Mobile Web Environment.
==> http://biguseof.org/cell-phones
What makes mobile content different from web-to-desktop content?
As will be described in detail below, mobile content is different in many ways from Web-to-desktop content. The mobile world is fragmented - there are thousands of mobile device models, with different form factors, operating systems, and browsers. On the Web this is not an issue. This means that even though similar technologies are generally used to build Websites for mobile devices and desktops and even though in some cases the same web server might also be used to send content to both, multiple versions of the mobile content need to be created, stored, and delivered.
In addition, website content is downloaded very differently to a mobile device than to a desktop browser in order to provide the desired end user experience.
Web Content on a Mobile Device.
The mobile device connects to the operator network.
Every mobile request goes through the operator's backbone.
Content server sends different content depending on device capability.
Web Content on a Desktop.
Desktop connects to the ISP.
ISP routes through the Internet to download content.
Content server sends same content for every request.
Device-specific mobile content-a monitoring challenge.
One of the most important differences between mobile and desktop-based web content is the need for mobile content to be tailored for the various characteristics and capabilities of a particular device. This added level of complexity affects development of monitoring strategies, and it must be taken seriously in order to truly understand how the full spectrum of end users accessing mobile content will experience it. Clearly this expansion of the scope of content monitoring is one of the major differentiators from a desktop-based web monitoring strategy. With literally hundreds of device types in circulation and more coming on the market each day, attempting to understand the end-user experience by manually testing content on each device is cost-and time-prohibitive; automated monitoring strategies are required.
What is the impact on performance monitoring?
In the web world, both the user interface and the delivery mechanism have been standardized for years.
However, mobile content must be routed to the user through an operator network, and additional operator.
Specific content may be added during the download. Also, different devices render content differently, so when the Web server detects a specific device type it may choose to send a variant of the generic content to the requesting device. Finally, different devices are capable of handling the various components of a download differently (for example, images, text, and third-party content) - which can dramatically vary download time.
This means that web performance-monitoring techniques that work with desktop-based web content will necessarily fall short in a Mobile Web Environment.
==> http://biguseof.org/cell-phones
Subscribe to:
Comments (Atom)