A deeper look at the Intel IvyBridge Ultrabook

I’ve spend a lot of time with Intel’s IvyBridge Ultrabook since I wrote my “First look at the Intel IvyBridge Ultrabook” post a couple of weeks ago. Intel wanted to get a pre-production Ultrabook in the hands of a few devs so they can dev with it and give some feedback on what development would look like when we have all those sensors at our fingertips.

I’m somewhat new to sensor focused development, but I know that I will be considering how I can use them in every app that I build from here on out. Determining the users location, determining distance of movements, supporting touch screen are all capabilities that we can design for from now on. I’m not suggesting that we build just for the coolness factor, but if the sensors make the app easier to use or make the user more productive then I’m all for it.

Being the career web dev that I am I first thought I would have little use for those sensors and even less demand for features that require those sensors. My limited exposure to sensors was back when I was in Bing Mobile, where I added turn by turn navigation to Windows Mobile 6.x. So that’s the first application I thought of when considering what I could do with all the new Windows 8 sensors. I could see someone rewriting a turn-by-turn navigation application with full sensor support. Instead of just using GPS to find the user’s location, they could use the accelerometer, gyro meter and magnometer to build a full functional app that simulates driving through the Bing Streetside maps. Bing does support Bing “Map Apps” and all you need to build a Windows 8 app is the Windows 8 SDK and .NET 4.5. So it should work. You could also host the Bing map application inside of a Windows 8 application and control the Streetside experience using events triggered by the sensors. You can learn more about all the sensor support that is included with Windows 8 from the “Supporting sensors in Windows 8” blog post written by Sinofsky.

Intel isn’t ever going to mass produce these Ultrabooks, they just built them as a prototype to show other manufacturers what can be done with Intel components. The biggest barrier that I see hardware manufacturers overcoming is the fact that every developer has spent a ton of time perfecting their workstation and the Ultrabook doesn’t easily fit into that space. We spend very long stretches of time at our dev machines and need something that is comfortable and not going to kill our bodies.

The number one problem is that this Ultrabook doesn’t support a docking station. You’d therefore need to connect and disconnect every time you want to dev for any length of time. My normal machine is a Lenovo W510. It’s big, it’s heavy, but it’s a great dev machine. I have a docking station at work and a docking station at home, each of them have 2 monitors, a wired connection and a ton of USB devices (hard drives, headset, digital audio interface, etc). I just undock, throw it in my bag, drive to work, grab out of my bag and re-dock. I also dock and undock all the time throughout the day, mostly just to grab a focus room to do an interview or triage or whatever. It only takes a few seconds to dock and undock and I can’t imagine connecting and reconnecting all the components it all the time.

Something to consider when considering an Ultrabook for your development needs is the number of USB and mini-HDMI ports. Some models that I’ve seen only come with a few of each, so just make sure there’s enough to meet your needs including all your peripherals and multi-monitor configurations.

For an Ultrabook to be a real dev machine it is going to need the following:

  • Docking station support with at least 8 USB 3.0 ports and multi-monitor support
  • Network adapter for wired connections