Popular Posts

Showing posts with label web content monitoring. Show all posts
Showing posts with label web content monitoring. Show all posts

Wednesday, February 8, 2012

Tablet Problem? Or Tablet Opportunity?


Yes, it’s another form factor, and more operating system permutations, still more network connection considerations, and additional development expense. But tablets could actually be a bright spot for content owners looking to attract audience and advertising dollars.

This past holiday season, iPad users showed themselves to be valuable customers, buying more and spending more than other mobile shoppers. And a number of studies indicate that tablet users are avid content consumers as well.

More than three-quarters of tablet owners use their device every day, on average for 90 minutes. More than half use it daily to get their news, and many now spend more time on news than they did pre-tablet. In fact, the only thing they’re more likely to use their tablets for than news is to browse the Web.

These numbers are likely skewed, as most current tablet owners have pricey iPads; they tend to be higher-income, better educated, often middle-aged consumers. As the market expands down to lower-priced Kindle Fires and others, tablet demographics will likewise gravitate toward a more mass consumer profile.

Read More: http://keynote.com/benchmark/SaaS/article_three_screen_optimization.shtml

Wednesday, August 17, 2011

Web Performance Varies by Geography and Network

Unlike Web content downloads to desktops, mobile downloads can vary dramatically based on time of day, network operator used, and geographic location. For example, a mobile Website can take twice as long to download in San Francisco as compared to another operator in New York, London, or Tokyo. If a content-monitoring strategy does not include monitoring web content from various geographic locations, it is impossible to know what the end users are experiencing.

In the Web world, both the user interface and the delivery mechanism have been standardized for years, keeping mobile browser compatibility in mind. 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.

Read More