High Dynamic Range Computing

Posted on 23 April 2011, Last updated on 10 August 2013 by

There are two very popular and very different Internet  viewpoints out there.  One shows social, app-centric, dynamic, location-aware mobile environments and the other looks out on high quality, feature rich work environments. [More on the two Internets and Web experiences here] Computing hardware platforms have crossed over from both sides but there’s still a problem getting apps across the bridge between the hand to the desktop. This article, adapted from a presentation given at Mobile Monday, briefly highlights how a new OS could be the bridge that enables high dynamic range computing, HDR Computing.

The presentation is available online.

You Only Have One Time-Line

You have one timeline of activities and at certain points, they mix and crossover. There’s little chance in the modern life to separate the two works of work and home and as a result, the need for applications, documents and content to be synchronized across different devices is greater than ever.  The phone becomes the pivot point for the data but that data needs to extend across an increasing number of devices. Devices and applications tend to stitck to both work and play timelines making them inseparable.

Why we need multiple devices

What you can do within 3.5″ 11 inch is limited in terms of screen and computing thermals, input mechanisms and battery life. Smaller devices are becoming  more capable but physics gets in the way of complete convergence.


This shouldn’t be a surprise to anyone. For example, to write this document, I had to sit down, use a 10 inch screen and a touch-typable keyboard. As I type this, my tablet is next to me.

Why is my tablet next to me?  Because it does some things better than my laptop and some things that my laptop just can’t even attempt to do. SMS, WordPress notifications, Gtalk, Twitter are all examples and they work better because of always-on, applications and hardware like sensors and camera. Plus, PCs tend to run wild and uncontrolled when there are multiple apps running. That reduces battery life for critical work-related processes. The continuity between my two devices is split. Each device has a limited dynamic range in terms of software and hardware capabilities. It would be nice to have a single device that offers the best of both worlds but based on physical issues mentioned above, it’s not possible but what if there was an operating system, a hardware platform and an applications library that could span different usage models? The useful range of any device would be extended into an HDR device.

There are no options today.

A PC can’t idle down to 200mw power drain and enable always-on capability. Most PCs and desktop software don’t support location. You can find PC apps but they are big and often do too much resulting in expensive software products. They often take 10 minutes or more to dowlnoad and install which limits the try-then-buy(and recommend) model.
On the other hand, ARM CPUs that many tablets and nearly all phones are based on don’t have the CPU power to enable advanced processes. Video editing for example. Mobile operating systems also offer relatively shallow apps. Take a look at the office suites out there for mobile operating systems. The free MS Office Starter solution on a PC is stunning by comparison. Multi-user logins, multiple on-screen apps, drag and drop, encryption, USB host, rollback, remote desktop, VPN support, networks drives and many other features are either poorly implemented or just don’t exist on mobile operting systems.

Hardware is crossing over.

While it’s not possible to get hardware that spans mobile and table-top computing scenarios today, it may be possible very soon. Here are some examples of what’s happening in the hardware market.

  • The camera in my Nokia N8 has a better quality sensor than my 3 year old bridge camera
  • ARM CPUs are reaching the processing power of low-end X86 platforms
  • X86 platforms are reaching the idle battery drain of the high-end ARM platforms
  • You can run Android on X86 and, Ubuntu on ARM
  • The screen, storage, radio, battery, cooling, and production technology and processes are the same for both platforms.

Mobile operating systems are pushing into desktop form factors.

Desktop operating systems are pushing into mobile form factors

Add new Operating Systems to enable HDR-Computing

Both mobile and desktop operating systems today were written for one target segment and then, in order to explore new markets expanded from there. This strategy tends to result in compromises as desktop features are bolted on to mobile operating systems and mature desktop operating systems suffer from ‘bloat’ and legacy hardware support. An operating system built for HDR Computing has to be built from the ground up for its intended purpose. To span multiple hardware platforms, offering a ‘best of’ feature set that can enable both mobile and desktop operating modes through application cores that re-skin based on that operating mode, screen size and input method.


Companies that sell products in laptop, desktop and mobile markets will NOT want to collapse their ecosystems into one. Separation helps multiple sales.


There are clear opportunities. Some are very heavyweight.

  • HDR Computing is disruptive
  • HDR Computing could enable a migration to cheaper, quicker product manufacturing, reduced support costs.
  • HDR Computing enables something that Joshua Topolsky was talking about recently – Continuous Client.
  • HDR Computing enables Single chassis, multiple bodies (Cost, time savings for OEDs)
  • HDR Computing has obvious developer advantages. (One core, multiple uers interfaces,multiple markets)

Not just for Mobiles and Desktops.

There are multiple markets where HDR Computing could extend.

  • Cars. When one platform / OS is approved, it can be used with multiple skins, features, options.
  • Cameras. Digital cameras are about to go through a big change via Internet sharing
  • TVs. A huge market.
  • Gaming devices. A huge market.
  • Vertical markets – Hospitals, Blue Light sector (one security approval – many devices)

There are Barriers – and they are Expensive

HDR Computing is not easy and platforms, operating systems and applications will take years to mature. Major hurdles exist.

  • Traction. It’s a huge leap that will require massive investment in marketing and market confidence.
  • Silicon engineering and thermals. We can just about reach notebook processing power for short periods of work in a handheld device. Controlled platform is key. Modular systems also solve the problem. (High power when docked for example)
  • Applications – Who wants to write applications for a fledgling operating system?
  • One-size doesn’t fit all? Often, single-use devices with dedicated operating systems and applications are better.

Who has an Opportunity?

There are some obvious players in the market that could take on HDR Computing. As mentioned above, HDR Computing is a Red Flag for companies that make profits in multiple mobile and desktop markets.

  • HTC – Mobile only
  • Intel – Sell HDR silicon.
  • Google – Successful in mobile devices only at present. Looking to expand.
  • Nokia – Mobile only although their ‘distruptive computing’ group might find themselves with a lower budget / BG this year.
  • A very, very big startup!

Obviously companies with large cash reserves also have an opportunity. Samsung and Apple come to mind immediately but their opportunity to be distruptive is limited due to their existing revenue streams on multiple different operating systems. ARM is a company that sells licenses but could gain from creating a sister company (or partnering, being taken over or taking on another company) that creates products. To compete with their own licensees would be a complex and risky business strategy however.

What’s happening today?

Five operating systems to watch are:

  • Ubuntu
  • MeeGo
  • Honeycomb branch of Android
  • Windows 8
  • WebOS

All of the above operating systems have an opportunity to become an HDR operating system. There is also work going on in other areas.

  • Componentised apps (multiple UIs, one core) already exist in iOS and Android
  • ARM Cortex A15 quad-core hardware – Above netbook processing power, below netbook idle usage.
  • Intel Atom – Moorestown, Medfield idle into ‘near zero’ remove PC history, power up to above netbook processing power. Turbo, thermal controls.
  • AMD – APU work. GPU, HD decoding, GPGPU support. Small die. (Still old PC compatability though)
  • Apps. Honeycomb signals start for serious Android app developement.
  • IOS Serious app development ‘trust’ is already there.
  • MeeGo App store.
  • WebOS? QNX? Lets wait and see.
  • CUPP Computing – innovative approach using dual CPUs in one system (can support multiple concurrent OS)
  • Hardware Virtualisation

What about HTML5?

It’s another opportunity. But is it too removed from hardware and multiple types of browser may stall the process. Energy and speed efficiency gets harder, the further it is removed from the hardware.

The cloud isn’t mobile yet.


HDR Computing is a major opportunity. It proves that the mobile and desktop markets for hardware, operating systems and applications are not as safe and stable as many might think and could be turned on their head. It could simplify the process for manufacturers, consumers and applications developers and enable the idea of  ‘continuous client’ through easier state synchronization. It requires a new style of hybrid silicon platform that can idle at very low power levels but when required, can produce desktop-level processing levels. These new platforms will be very tightly coupled to an operating system and possibly developed in unison. There are opportunities for new players but the costs and timescales are prohibitive for all but the largest and best-positioned companies.

11 Comments For This Post

  1. UMPCPortal says:

    High Dynamic Range Computing http://www.umpcportal.com/?p=23641

  2. Gretchen Glasscock says:

    High Dynamic Range Computing: There are two very popular and very different Internet  viewpoints out there.  One… http://bit.ly/fW7AWj

  3. Emanuele ∞ Vulcano says:

    RT @umpcportal: High Dynamic Range Computing http://www.umpcportal.com/?p=23641

  4. Tina says:

    High Dynamic Range Computing | UMPCPortal – Handhelds, Tablets …: Componentised apps (multiple UIs, one core) … http://bit.ly/hzdq4n

  5. Alltop Mobile says:

    High Dynamic Range Computing http://bit.ly/fW7AWj

  6. Mobixy says:

    High Dynamic Range Computing http://bit.ly/fW7AWj

  7. rabs says:

    Well, Linux have always been cross devices, and Ubuntu / MeeGo / WebOS (?) are finally bringing it to general audience.

    I mostly use the same softwares on my n800 and desktop.
    The philosophy: software are focused on a task, efficient and highly customizable. Complex tasks are done by scripting many tools.
    So it’s just different settings/scripts for different devices, with a frontend/launcher for touch based devices.

    For example, transforming a generic text editor to a “WordPress app” is just a matter of writing a few scripts/macros (using other libs/tools, sending a preview to the web browser, etc).
    And it can be fully personalized:
    – saving the posts in a special directory/repository
    – using custom macros/scripts for generating parts of the content, checking things

    And all that doesn’t add bloat to the text editor, it’s just started with a specific config file.

    Though, it doesn’t fit in the Apple-style marketplace philosophy.

  8. aftermath says:

    I have to agree with a lot of this. Become familiar with the Debian distribution of GNU/Linux. Five years ago I was running it on a Zaurus, an old PDA, a few laptops, a desktop, multiple tablet PCs, a 16 node compute clusters, and a whole pile of embedded systems. I never bothered to call it “high dynamic range”, but it’s still an idea whose implantation is already over five years old.

    The problem is not the functional back-end. The problem is that front-end that is exposed to the user. User Interface solutions found in today’s crop of FadWare, i.e. iOS, Android, and MeeGo are legitimately terrible. There is absolutely no innovation, and people who get excited about this as the next generation of computing obviously hating computing and everybody who enjoy or depend on it. Fortunately, there are some much better ideas for user interface out there coming down the line and better hardware than crappy old touchscreens.

    Finally, I think that the general ideas behind “High Dynamic Range” computing are pretty silly as is the attempt to reify it into something more substantial than the collection of loosely related insinuations that it is. What we really need is better, more efficient software everywhere. That’s all. Efficient software will run well on all hardware, and you can take as an implication of that the fact that Debian must be pretty efficient. Modern software usually sucks. At best, it simply nullifies any performance gains that we might have otherwise enjoyed by upgrading to the newest generation of hardware. At worst, it stabs Mr. Turing in heart by providing a pretext through which to prematurely obsolesce otherwise useful hardware (I’m looking at your Apple and Google). Speaking to the same point, it’s the user interfaces which are not very efficient. Actually, the modern desktop operating system is in fact VERY efficient, but the modern handheld operating system IS NOT when it comes to UI and UX. For the most part, consumers aren’t actually very good about thinking about these things, mostly because they’ve already eaten the marketing dog food offered by companies, and they follow sources of information that are there to speak on behalf of the companies who sell products. These things aren’t very hard to think about, but if you look and how people spend their money and what they spend their time talking about, using. or lusting after, , it’s clear that they can’t quite grasp it despite its simplicity.

  9. Clio says:

    Chippy, you and Joshua Topolsky’s thinking are still bound, perhaps, by a subconscious assumption that the physical CPU/RAM/storage MUST only use its dedicated physical display. But in fact, it’s not neccessary.

    I think it’s stupid we have to hold the CPU+heatsink+Hdd, etc…, in our palm when all we want in our palm is the display and some form of input. It is also stupid that we end up carrying around so many screens everyday.

    Instead, we should have 2 group of devices:

    Group 1.) the processing blocks
    This will include the Atom/ARM/Fusion APU, GPU, RAM, storage, OS & Big battery. It may have some ports, but no screen or user-I/O devices, because this module is supposed to stay in the pocket (or holster, if you have to). That will be a few hundred grams off the wrist, and the processing module can have a little more weight/size allowance. The OS only deals with a logical (or virtual) display, not a physical one.

    With virtualisation technology like VMware Infrastructure (http://download3.vmware.com/demos/esxi/VMware_ESXi.html –> click infrastructure at the top of the presentation or just watch for a few minutes), the OS and hardware is further detached, allowing OS sessions to be moved among processing blocks, and also adding/removing extra processing blocks into the group becomes possible.

    Group 2.) the I/O devices
    May include screen, touchscreen layer, audio in/out, keyboard/pointer and maybe couple of usb ports for easy access. It should be encased with just enough CPU and RAM to handle pairing the already-rendered virtual-display described above, to the physical pixels available. Also manages multiple pairings and handles I/O with user.


    If that happens, the Desktop LCD & Keyboard, Tablets, smartphones and netbooks can all be Group 2 devices, all very lightweight when on the palm, and all have access to the OS sessions hosted by the Group of processing block(s). I said “group of processing block(s)” because when you’re on the road, you may only have an Atom/ARM processing block on you, but when you get home, you may have an i7 behemoth processing block, at which point, you can drag & drop the OS instance you carried all day on the Atom onto the i7 and carry on with what you were doing.

    All the above happens through local Wifi, not via internet because internet response time and bandwidth is still not up to this kind of usage.

  10. Clio says:

    That’s why Intel’s WiDi Technology is exciting for me. But at the moment, the receiver is still too big to integrate into any mobile screens such as tablets.

  11. Mike Cane says:

    You mention webOS but not HP as a possible beneficiary of this strategy. Weird. Have you already forgotten HP pioneered pushing Asus’ netbook concept into a higher price range with its Mini line? There was Asus, that Cloudbook, and HP at the time. Cloudbook was knocked out as crap. HP got ragged on for that crap VIA CPU, which they quickly ditched and went on to sell quite well, IIRC, and paved the way for others — including incompetent latecomer Sony! — to jump in. HP in fact might be the pioneer here: webOS on phones (Pre 3 and Veer), tablet (TouchPad), and their PCs (desktops, notebooks). If they get non-touch seamless sharing going between those three (with the option of *not* using The Cloud, so hardware-locally), it’d be major.

Recommended Reading

Top Ultra Mobile PCs

Dell Latitude E7440
14.0" Intel Core i5-4200U
GPD Pocket 2
7.0" Intel Core m3-8100Y
GPD Win 2
6.0" Intel m3 7Y30
Viliv S5
4.8" Intel Atom (Silverthorne)
HP Elitebook 820 G2
12.5" Intel Core i5 5300U
Acer Aspire Switch 10
10.1" Intel Atom Z3745
Acer Aspire E11 ES1
11.6" Intel Celeron N2840
Lenovo Ideapad Flex 10
10.1" Intel Celeron N2806
Microsoft Surface Go
10.0" Intel Pentium 4415Y
LG G8X THINQ Dual Screen
6.4" Qualcomm Snapdragon 855