For a long time Microsoft was in an enviable position in the smartphone space. It had almost all the pieces of the puzzle you’d expect for delivering a truly unique smartphone platform. It had the historical perspective, from the initial days of PocketPC, to Windows Mobile platforms, the software giant hasn’t exactly been uninvolved with the smartphone space. It is and remains first and foremost a software company, while other players come either the web or primarily hardware-focused perspectives. Lastly, it had the relationship with OEMs like HTC already, willing to commit to radically different platforms. It seemed like execution was just a matter of lining up all those assets and clicking go.

With Windows Phone 7, we saw Microsoft make a clean break from Windows Mobile and begin to morph the mobile experience from something tailored largely for users wanting a smartphone that emulated the Windows experience as much as possible on a smaller screen to a mobile-driven UI with a completely ground-up look at what needs to be part of a smartphone OS. WP7 was a radical re-imagining of Microsoft’s mobile story at a point in the smartphone explosion where it wasn’t very clear who would emerge victorious and who would fizzle out. I remember being at MIX10 two years ago and watching the elements of WP7 taking shape, and while that launch didn’t necessarily have every last feature needed to guarantee success, Windows Phone is still around and a few other big players notably aren’t. At that point Microsoft essentially started anew and since then has largely remained something of a number three in the smartphone OS space while iOS and Android have continued charging ahead. The question now is just how Windows Phone 8 will upset that balance.

Hello NT Kernel - Bye Windows CE

Superficially Windows Phone 8 is very similar to Windows Phone 7.5 and 7 that came before it, but what’s different under the hood is dramatic. The move away from the Windows CE kernel and onto the same NT kernel as Windows 8 and RT run will have far reaching implications for the platform that won’t be immediately visible to users, but is nonetheless the core of what’s new in Windows Phone 8 (henceforth WP8). It might seem odd to start out the discussion about WP8 by talking about this, but really this is the single largest change in this revision.

For Microsoft, the break from Windows Mobile wasn’t really as clean as it probably would have liked. In fact, large parts of WP7 were built atop the exact same framework (and the same CE kernel) that drove that platform. The result was a software stack without the kind of abstraction necessary to make moving between silicon an easy move, and as a result WP7 hardware always seemed to lag behind what was relevant at the time in other camps. While the continual refrain in the mobile space is that specs don’t matter, the reality is that the truth couldn’t be further away. Battery life improvements, newer air interfaces (though we saw LTE support get added at the tail end of WP7’s life cycle for the Lumia 900), better camera performance, better video performance, and of course better overall performance all starts with that combination of SoC and kernel.

For WP8 the move to the same “shared core” (NT kernel) as Windows 8 and RT brings numerous improvements. First is that improved level of hardware abstraction which makes moving between SoCs easier. When I heard about this, I joked that at present that really only translates into less work for Qualcomm (WP8 is still a Qualcomm-only camp), but at the same time in theory work done by other silicon vendors to make their SoCs run Windows RT well translates to work done toward the same goal for WP8. I won’t speculate too much about the exclusivity implications, but that portability for the platform is there.

The other improvement from moving to the NT kernel and away from CE is multicore support. Win NT’s scheduler scales nicely even up to 64 cores, and while we’re thankfully a ways off from seeing more than 4–8 logical cores on mobile SoCs, the platform is now there to support it. The other angle is that obviously Microsoft knows how to write a good scheduler, whereas we’ve seen some other platforms only recently start to get threading ironed out for multicore SoCs. The other story is easier driver migration for both the OEMs and other hardware or silicon partners, obviously bringing WDDM to WP8 makes sense given silicon vendors already working on this for Windows RT and Windows 8.

Better sandboxing support in the NT kernel also enables the use of development in C/C++ and thus sandboxed execution of native code. The major complaint back in the WP7 days was always that developers had to work with managed code in a managed environment with Silverlight. Try as Microsoft did to hide the difference between the first party native apps and third party ones, there was always a detectable and uncanny difference in feel and responsiveness for me between apps that were clearly Silverlight or clearly XNA or first party. That’s a really subtle WP7 complaint I wager most users never noticed, but the goal is to eliminate as much as possible of that in WP8.

Finally the chassis spec has also changed a bit with WP8 as a result of the changes in both kernel and higher level platform support. Chief among those is the change in which display resolutions OEMs can build for WP8, which now includes 720p and WXGA in addition to WVGA, which means there are now two aspect ratios for WP8, both 15:9 and 16:9, more on that later. Support for SD cards is also a big new feature in WP8, though this is an optional thing for OEMs, and interestingly enough neither of the flagship WP8 launch devices (Nokia Lumia 920 or the HTC 8X) include one. The spec also explicitly calls out Snapdragon S4, at present from what I can tell all launch devices are S4 Plus, either MSM8960 (28nm dual core Krait up to 1.5 GHz with Adreno 225) or MSM8x30 (28nm dual core Krait up to 1.2 GHz with Adreno 305). Larger displays also beget more RAM, up to 1 GB minimum now. The rest of the spec is largely the same — dedicated buttons for navigation, a camera button if you include a camera, WiFi, bluetooth, and so forth. I would’ve loved to see 5 GHz WLAN become a mandatory thing for the spec, but it seems as though most of the higher end WP8 devices will include it anyway as a result of widespread component availability.

Windows Phone 8 Chassis Spec
Component Minimum Specification
SoC A "powerful" Qualcomm Snapdragon S4 dual core processor
GPU DirectX graphics hardware support with hardware acceleration for Direct3D using programmable GPU
RAM 512 MB for WVGA, 1 GB for 720p and WXGA
Storage 4 GB NAND, optional microSD with SD or SDXC support
WLAN + BT 802.11b/g (n optional), Bluetooth (no mandatory spec)
Display 800x480 (WVGA), 1280x720 (720p), 1280x768 (WXGA), 16bpp minimum, capacitive multitouch with 4 or more simultaneous points
Sensors Accelerometer, proximity, ambient light (ALS). Optional magnetometer/compass, gyro.
GNSS GPS mandatory, GLONASS optional (S4 includes support)
I/O microUSB 2.0, 3.5mm headset jack with 3 button support, vibration
Buttons Dedicated start, back, search, power/lock, volume up, volume down
Camera Rear-facing camera with LED or Xenon flash, AF, and an optional front-facing camera, both with VGA quality or better, and a dedicated camera button for quick access. (Note: While the Windows Phone 8 chassis specification does not mandate either a main camera or a front-facing camera, all of the Windows Phone 8 launch devices will have both.)

I think it’s fairly easy to argue that the kernel and chassis spec make up the core of what’s new in WP8. From my point of view, this is the bulk of what’s really different about the platform, and at a high level WP8 is essentially an entirely new smartphone OS simply styled the same as WP7.8. As always, however, it’s possible to nail all of this but still not execute well elsewhere, and this is where we turn to the rest of the WP8 story.

Live Tiles, Lock Screen, Maps, Hubs
POST A COMMENT

96 Comments

View All Comments

  • R101 - Wednesday, October 31, 2012 - link

    Is there any info on bluetooth support - does Windows 8 provide phonebook entries and call history over bluetooth or not? Reply
  • R101 - Wednesday, October 31, 2012 - link

    Windows PHONE 8, just to be more precise.. Reply
  • Jorange - Wednesday, October 31, 2012 - link

    Just to show I have no inbuilt bias, I currently own a Lumia 800, Nexus 7 / iPod Touch and Windows 8 & Linux PCs, in the past I've used OS X.

    A dual-core S4 (good) / Adreno 225 (Average) / RAM - 1 GB (ok) 512 MB (not good enough) These specs are just about passable for a head-end phone, but the quad-core S4 Pro with Adreno 320 is a big improvement, the A6 is excellent. ARM A15 SoC like the Exynos 5250 are already on the market, although not in a phone, Tegra 4 and Exynos 5450 will launch in Q1 to Q2 2013 and will destroy a regular S4.

    People may argue that WP8 is smooth, big woof so was WP7, and so is iOS and thanks to Jelly Bean so is Android. When it comes to gaming, web browsing, apart from Sunspider (cough cheat) WP8 will age quickly. There are already reports that page loading and general app opening times are more sluggish than iPhone 5 / high-end Android, which Windows Phone like to hide with transition animations, which can irk after a while.

    Will all my above comments be rendered mute by a yearly Hardware update cadence? That is the big question, if not WP8 will fail to offer the high-end attractions its rival platforms will offer, such as cutting edge games / 1080p video at 60 FPS etc because of lower spec hardware.
    Reply
  • von Krupp - Wednesday, October 31, 2012 - link

    One of the biggest differences between WP7 and WP8, though, is that Microsoft built an upgrade path into the latter. WP7 was basically locked onto the launch hardware. From what I understand, WP8 can be scaled to up to 64 cores, and supports resolutions greater than 720p. I'm sure GPU and RAM improvements will be included. Reply
  • Dorek - Friday, November 02, 2012 - link

    "People may argue that WP8 is smooth, big woof so was WP7, and so is iOS and thanks to Jelly Bean so is Android. When it comes to gaming, web browsing, apart from Sunspider (cough cheat) WP8 will age quickly."

    Do you only know how to read numbers, not words? Did you see the part of the review where he mentions how hardware support will be much broader for WP8? It has support for up to 64 cores. It won't age any more quickly than Android or iOS.
    Reply
  • Freak01 - Wednesday, October 31, 2012 - link

    Once again, and I'm sure there are others who would would really like to see a proper review of the new Nokia. Anand...? Reply
  • ex2bot - Thursday, November 01, 2012 - link

    Incidentally, isn't calling Apple primarily a hardware company a wild oversimplification? Modern Apple software: OS X, iOS, iPhoto*, iMovie*, iDVD, GarageBand*, iTunes, Pages*, Numbers*, Keynote*, Safari,* QuickTime, Aperture, Final Cut Pro, Motion, Logic, DVD Studio Pro, OS X Server, Remote, Apple Store, iBooks. Not to mention the dozens of applications associated with their operating systems.

    * Versions for both mobile and desktop
    Reply
  • JNo - Friday, November 02, 2012 - link

    "For the platform WP8 is absolutely an evolutionary step, rather than another dramatic re-imagining of Microsoft's vision for smartphones."

    "At the same time WP8 feels like a dramatic update over WP7.5"

    These sentences in the conclusion seem somewhat contradictory... there might be good reasons why they are not but, if any, they are not clear to me.
    Reply
  • tipoo - Saturday, November 03, 2012 - link

    Since it's becoming very apparent that some browsers optimize around certain browser tests, wouldn't it be better to just have page load speed comparison benchmarks with a few well known websites, or an aggregate of a few? Reply
  • righteousdesigner - Saturday, November 03, 2012 - link

    Can anyone tell me if TMO version of HTC 8x will be LTE futureproof like GSN2? Reply

Log in

Don't have an account? Sign up now