Less Mobile Bandwidth and More Mobile Battery Life
If you're new here, you may want to subscribe to the RSS feed for this blog. Or you can subscribe to a combined news feed for all SMM publications. Thanks for visiting!
Hot Mobile News
Verizon Wireless and Samsung announced today that its new V CAST Mobile TV service will be available on the new Samsung SCH-u620 mobile phone. This is expected to be available in the first quarter of 2007.
The present invention discloses a system and method for decoding barcodes using mobile device. Generally, the barcode image is acquired via a digital camera attached to the mobile device.
The system enables drivers and passengers to use Bluetooth-enabled cell phones as hands-free devices linked to a vehicle’s audio system; access and play music — from MP3 devices; utilize personal navigation devices; control onboard audio and multimedia systems; handle climate-control settings; and more.
There are two striking differences between Desktop PCs and Mobile Devices. The first is that extra bandwidth is usually very economic for desktop PCs. On the other hand, extra bandwidth for mobile devices can in some cases be punitive. The energy source is an even bigger differentiator. Energy for desktop PCs is readily available without limit and at very low cost. For mobile devices, a very limited and finite energy source is provided. These two differences should be uppermost in the web designer’s mind as they design for these two worlds.
What this all boils down to is the need to ideally deliver to mobile devices only the content/bandwidth they can use. This suggests an important step in delivering Web content to mobile devices. The ‘One Web‘ approach states that a single URI should deliver satisfactory user experiences whatever device is being used.
Current thinking is that two steps are involved in this. The first is device detection by the server. Once some essential parameters of the device are detected, this will help the server determine how the URI content should be best served to that device.
The next step is what is called adaptation. Through this the server will adapt the URI content to be most suitable for that device.
If the bandwidth/battery concerns discussed earlier are important, this adaptation process should deliver very much less of that URI content to a cell phone than it does to a desktop PC. This differentiation will mean that from the same URI, a cell phone will download very much less than will the desktop PC.
If this is a correct description of the adaptation process, the question of whether these vastly different devices receive very different versions of the same URI content or different associated URIs seems almost a matter of personal choice. This is why the Multi-Web approach with associated URIs recorded in a AGI (Array of Graphic Identifiers) is being suggested. It involves fewer technical challenges and is a much more robust approach.
For example, a very simple approach would be to have the AGI include 5 URLs providing optimized content for 5 typical devices such as
| Type | Screen Width in pixels |
| High-res Desktop (PC) | 1280 |
| Low-res Desktop (PC) | 800 |
| PDA - larger | 480 |
| PDA - smaller | 320 |
| Cell phone | 160 |
The ‘Crunch’ questions on this boil down to the following:
- Should bandwidth concerns limit the URI content delivered to very small mobile devices?
- Should battery capacity concerns limit the URI content delivered to very small mobile devices?
- Given the answers to either 1 or 2, should adaptation deliver different URI content to different devices?
- If the answer to 3 is affirmative, is the Multi-Web approach a reasonable alternate to the One-Web Principle?
Tags: Mobile, mobile device, one web
Go To Top
in the SEO Services Marketplace
BPWrap
