Dispelling The Apollo Update FUD

Seriously, the debate over WP Apollo update and its availability for current devices has reached cacophonous levels. None of that is actually needed and I can’t help but suspect that most of it is carefully orchestrated FUD. There was an unusually high level of negative criticism even before the WP platform was launched in Q4 ’10, with bloggers trying to declare it DOA. The vitriol continued till the NoDo update but dwindled thereafter with the realisation that Windows Phones were not selling too well and hence was not a threat to the established players. The sudden rise in vituperation against the platform now, is therefore a clear sign of unease in the minds of Android and iOS aficionados as there is a perceived rise in mind share (even if not market share) of Windows Phones and Nokia Lumia devices.

However, I’m truly surprised at the insipidness of the arguments being put forth in the Apollo update debate. Most of the bloggers, from harsh critics to unbelievers to wolves in sheep’s clothing (no prizes for guessing who), are hiding behind ‘unnamed sources‘ in their negativity, without putting forth any worthwhile hypothesis. Even Mary Jo Foley has her ‘sources’ indicating that Apollo will not be available to 1st and 2nd Gen devices. But sources can be wrong. Not everyone in a large company like Microsoft knows everything. Why, just the other day my ‘source’ at Nokia claimed that Lumia 900 will be available in India in May ’12 at the price of INR 24,000 (approx. $460, unlocked of course). When I expressed incredulity at the price, it was explained that there was a feeling amongst Nokia India executives that they had bungled the 710/800 pricing by launching it at a high price and then slashing it drastically soon after. They didn’t want to do the same mistake with 900 and 610 and hence the low price. Well, that was a perfectly plausible explanation and I almost broke the ‘news’ on WP Sauce, but for my preoccupation in my day job. However, two days later, the source apologised and retracted the earlier claim saying that it was just wrong information. Lumia 900 will come in May alright but the price will be a conservative INR 29,000 – 30,000. (Oops, did I just leak a Lumia launch news?). So, the bottom line is, that sources can be wrong. In the Apollo Update case, the sources are more likely to be wrong than right (more on that later).

I am also surprised at the complete lack of understanding by these ‘negative’ bloggers about how software works vis-à-vis  hardware. They are all trying to project that it will be technologically impossible to upgrade the present hardware to WP8 because of the changes being made in software. Nothing can be more ridiculous than that. They have forgotten that the HTC HD2 was never supposed to run WP7 but ROM chefs at xda-developers managed that without even as much as breaking a sweat. They also forget that Android OEMs routinely express inability to update older devices to the latest dessert flavour but then they relent if the clamour for a successful older device grows loud. Most of these naysayers have a technical background (unlike me, my day job is further removed from technology than you can imagine), yet they don’t seem to understand that enabling a software for a certain hardware is predominantly a matter of choice, not of technology. I say predominantly, not entirely, because some features like 1080p video recording are obviously dependant on hardware. But that’s not the issue here.

Let us also examine what changes Microsoft will bring in WP8 and whether any of it poses a technological challenge. The three most important changes (known/speculated as of now) are 1) support for multiple core processors, 2) support for different screen resolutions and 3) closer alignment between Windows 8 and WP8 software. There is already enough evidence in Gingerbread, ICS as also iOS 5, that the first two features can easily be managed simultaneously on a variety of hardware, both old and new. The third major change is largely a software issue and if Microsoft can make Windows 8 to run on a variety of hardware and chipsets/processors including ARM, there is no reason why they cannot do it for WP8 too. All the other changes are also going to be software related tweaks which pose nothing more than a coding challenge to run on existing devices.

Well, if you agree with the aforementioned, that Apollo update to existing hardware is mostly a matter of choice, then lets discuss the probability of Microsoft consciously deciding NOT to exercise that option. To be fair to them, the only time they chose not to enable backward compatibility in any of their software (including DOS, Windows desktop OS, Windows Server OS, Pocket PC/Windows Mobile and Zune), was when they transitioned from WM6.5 to WP7. Let’s be serious – Do you really expect Microsoft to dump backward compatibility once again with the same OS, that too within two years? I have no empirical evidence to suggest so and hence I am sanguine that Apollo will come to all existing devices.

The question does remain though, that why doesn’t Microsoft come forward and issue a statement to dispel the clouds of FUD around the issue. Well, the answer to that is simple. They simply cannot make the announcement now because it is not their decision alone. All the OEMs (and carriers in USA) have to also agree 100% before they formally announce it. The decision to support all existing third party apps in WP8 was theirs alone and hence they have done it unequivocally. The same is not the case for OS upgrade. Unfortunately for Microsoft, Windows Phones have not sold very well and they cannot talk to OEMs from a position of strength. They still could do so if Lumia 900 turns out to be a super hit device, but for that we have to wait a little longer. There is one more reason that is preventing a formal announcement and that is the question of price of the Apollo upgrade. Major version upgrades of all Microsoft software has had to be purchased by the user and there is every possibility that the same will apply to Apollo. Hence Microsoft and all OEMs have to reach a consensus on the price and how it will be shared between them. Nokia, for example, may even want to provide the upgrade for free but the others may not agree. Therefore, my friends, we must wait a little longer to see which way the cookie crumbles. But it will certainly crumble, of that you can be sure.

391 days ago by in editorial | You can follow any responses to this entry through the RSS feed. You can leave a response, or trackback from your own site.
About the

Tech enthusiast from India. Interests range from gadgets & technology to photography & music (listening only). Fan and critic of Windows Phones. Current device - Dell Venue Pro 8733.

  • Kach

    Good Post!I hope that microsoft and cariers will understand that we really need apollo update.Because happy coustumer = money.

  • Alternsti

    Good Post.  I’m hoping price upgrade from Lumia 800 to Apollo will not be to much.  Right now I’m really satisfied but I think and will not say no to Apollo upgrade whern available.

  • Bala

    nice article buddy . You showcased the truth behind. All these F*** android makers are creating this mess. 

    Windows Phone 8 will come to present both 1 and 2 nd gen phones for sure. 

  • waleonishmail


     Let’s be serious – Do you really expect Microsoft to dump backward compatibility once again with the same OS, that too within two years? I have no empirical evidence to suggest so and hence I am sanguine that Apollo will come to all existing devices. ”
    Good Article but here is where I think you are being optimistic while everyone is being pessimistic. MS has already said that apps will continue to “work” which is only applicable to developers who are designing apps really. For consumers using WP7 they will see fewer apps as developers specifically target WP8. This isn’t about breaking the compatibility but fragmenting the platform so they are allowed to move forward while still keeping the mango and tanog low end phones out there.

  • http://www.facebook.com/people/Olisaebuka-Maduka/1332058518 Olisaebuka Maduka

    I agree with almost everything you wrote here except for that bit about ‘price’; MS can’t afford to charge for WP upgrade when their major competitors, who also happen to have a major lead now i this race, are not charging at all.

    I especially agree with that piece about MS not being able to say a thing about the upgrade yet because the carriers and OEMs also need to give their consent. If you look at the fact that Apollo just went into testing (dogfooding) inside MS, then we can logically come to the conclusion that both the carriers and OEMs haven’t yet started testing it on their own networks and devices respectively, hence, will not be able to give any assurances even if MS is sure themselves.

  • Collin5

    At least one of your conclusions is flawed:

    Backward compatibility means that WP7 apps will run under WP8. As you stated, we have every reason to believe WP8 will run WP7 apps and thus be backward compatible. I am not aware of an official statement, but various MS employees have confirmed WP8 will be backward compatible.

    THIS DOESN’T MEAN, that WP8 will run on WP7 generation hardware. Of course this is technically possible (as you correctly outlined in your post), but just because it is possible doesn’t mean it is a good idea.

    Currently, developing for WP7 is like developing for a console. You have ONE OS and ONE well defined set of hardware specifications to program against. Keeping WP8 exclusive to WP8 hardware would maintain this model… it is identical to the transition from one console generation to the next (from the PS2 to the PS3). For developers, this is a very good model. It allows developers to concentrate on a single hardware architecture and optimize their products for it. This optimization effort is even more important for power and performance constrained devices like mobile phones. Being able to tell consumers that product A is a PS3 game (or WP8-App) and knowing exactly what hardware will be available to that PS3 game (or WP8-App) is a precondition to making any meaningful optimization effort economically feasible… it is what allows developers to give console gamers the best bang for their buck. When was the last time you expected a PS3 game to run on a PS2 ? That is what you are asking for, if you want WP8 on WP7 hardware.

    The Windows and Android models are the exact opposite of this. Under this model, a single OS version runs on a infinite number of varying hardware configurations. As a result, developers have nothing to go on. Under this model, economic realities always force developers to target the lowest common denominator. This is why PC games are only slightly better looking then their console counterparts, even though they should (based on modern PC CPU’s and GPU’s capabilities) totally destroy them.

    A practical example:

    WP8 hardware will support DirectX 11 and include native 3D software libraries like Unity. Even if it is technically possible to install WP8 on WP7 generation devices, you won’t get DirectX 11 support as the WP7 hardware simply can’t offer it. This will invariably force developers into the same “lowest common denominator” approach to software development. This is really bad for WP, as it sacrifices one of WP’s biggest  advantages over Android (and to a degree iOS). Unfortunately, market perceptions (the masses of people who have no idea what the consequences are of asking for WP8 on WP7 devices are) could very well force MS into offering WP8 for WP7 even though they would much rather not (and shouldn’t).

    This is my personal perspective on the matter as a WP7 developer.

    • https://twitter.com/#!/HotmailAlias Hotmail Alias

      I understand your concerns Colin, but something tells me these will not be as restrictive for the Windows Phone platform as you anticipate. Let me explain why. But first, lets get on the same page about this ‘WP8 hardware‘ that you talk about.

      Its been evident from the time Mango was revealed, that the next iteration of the OS will include support for higher specification hardware. So, when WP8 ships, several handsets will be launched with multiple cores processors, screens with higher pixel density, NFC, Bluetooth 4.0 radio, maybe better cameras and such. For arguments sake, lets call this class of devices as having ‘WP8 hardware’. But, this will not be the only new hardware. Nokia, for example will continue to push the envelope and launch Lumia 620s and 630s, maybe even 550s, in a bid to make Windows Phones more affordable for the first time smartphone buyer in emerging markets. Do you seriously think these new devices will continue to run WP7 or 7.5? I really doubt that.

      Its also certain that the WP8 hardware will support a different class of apps and games and developers would take advantage of that, ie, code for your next generation console. The current handsets will not be able to run them, leading to a degree of fragmentation in the platform. This will happen even if the current handsets get upgraded to WP8 (as you have explained). But why to talk of the future, such a thing is already happening. When Dell opted not to enable the compass in its Venue Pro (even though the hardware existed), a large number of compass apps became redundant for the DVPs. But did it stop developers from making compass and compass driven apps? When Microsoft added gyroscope support in Mango, the ensuing handsets had the hardware and apps are being written using the functionality which non gyroscope devices are not able to enjoy to the fullest. However, here its creditable of Microsoft to bake the Motion API in a manner that lower spec devices are not entirely left out. That also brings me to my third point.

      The approach of Microsoft towards WP OS has not been of exclusive segmentation, but of inclusive differentiation. Their developing Windows 8 as one OS to rule them all, also indicates the same. Heck, with their partnership with Barnes & Noble being announced, they might even have low power low cost e-readers running on Windows 8. This approach will be seen in WP8 also. If WP8 was only about making an OS for a higher class hardware, it wouldn’t have taken Microsoft 2 years to go from WP7 to WP8. No Sir, considering that they took something like 18 months to get WP7 up and running from scratch, there is certainly much more going on in the WP8 labs than just enabling better hardware. Time will tell to what extent they’ll be successful.

      Will that make it difficult for developers? To some extent, yes. Will it become like Android? No, that’s what Microsoft has been working on all this while to avoid. Their fashioning of Motion API and 95% apps running on 256 MB devices is ample proof of their intentions. So much so, that when WP8 is shipped, the lowest common denominator for developers will not be the lowest specification device, but a wide selection of devices with varying capabilities.

    • https://twitter.com/#!/HotmailAlias Hotmail Alias

      I understand your concerns Colin, but something tells me these will not be as restrictive for the Windows Phone platform as you anticipate. Let me explain why. But first, lets get on the same page about this ‘WP8 hardware’ that you talk about.

      Its been evident from the time Mango was revealed, that the next iteration of the OS will include support for higher specification hardware. So, when WP8 ships, several handsets will be launched with multiple cores processors, screens with higher pixel density, NFC, Bluetooth 4.0 radio, maybe better cameras and such. For arguments sake, lets call this class of devices as having ‘WP8 hardware’. But, this will not be the only new hardware. Nokia, for example will continue to push the envelope and launch Lumia 620s and 630s, maybe even 550s, in a bid to make Windows Phones more affordable for the first time smartphone buyer in emerging markets. Do you seriously think these new devices will continue to run WP7 or 7.5? I really doubt that.

      Its also certain that the WP8 hardware will support a different class of apps and games and developers would take advantage of that, ie, code for your next generation console. The current handsets will not be able to run them, leading to a degree of fragmentation in the platform. This will happen even if the current handsets get upgraded to WP8 (as you have explained). But why to talk of the future, such a thing is already happening. When Dell opted not to enable the compass in its Venue Pro (even though the hardware existed), a large number of compass apps became redundant for the DVPs. But did it stop developers from making compass and compass driven apps? When Microsoft added gyroscope support in Mango, the ensuing handsets had the hardware and apps are being written using the functionality which non gyroscope devices are not able to enjoy to the fullest. However, here its creditable of Microsoft to bake the Motion API in a manner that lower spec devices are not entirely left out. That also brings me to my third point.

      The approach of Microsoft towards WP OS has not been of exclusive segmentation, but of inclusive differentiation. Their developing Windows 8 as one OS to rule them all, also indicates the same. Heck, with their partnership with Barnes & Noble being announced, they might even have low power low cost e-readers running on Windows 8. This approach will be seen in WP8 also. If WP8 was only about making an OS for a higher class hardware, it wouldn’t have taken Microsoft 2 years to go from WP7 to WP8. No Sir, considering that they took something like 18 months to get WP7 up and running from scratch, there is certainly much more going on in the WP8 labs than just enabling better hardware. Time will tell to what extent they’ll be successful.

      Will that make it difficult for developers? To some extent, yes. Will it become like Android? No, that’s what Microsoft has been working on all this while to avoid. Their fashioning of Motion API and 95% apps running on 256 MB devices is ample proof of their intentions. So much so, that when WP8 is shipped, the lowest common denominator for developers will not be the lowest specification device, but a wide selection of devices with varying capabilities.

      • Collin5

        Thank you for taking the time to reply. So far, you haven’t convinced me. Before I address the issues you raised, I need to clarify the role hardware plays in this discussion, as we are not on the same page here:

        Things like NFC, gyroscopes, the compass, camera, BT 4.0 (basically all the things you mentioned and then some) are almost irrelevant in terms of fragmentation. Hardware variability of this kind is completely abstracted away by the OS, the exception being when a capability is omitted completely (compass in the DVP). Hardware that is this inconsequential I call “peripheral hardware”. Example: You can slap any camera you want on a WP7 phone (>= 5MP), it won’t make any difference to any app. Because all apps deal with peripheral hardware indirectly through the OS, no amount of software optimization efforts are involved. My point is, none of these things are related to what I’m talking about. MS might specify lower bounds for some of these things (like the lowest camera resolution), but only to ensure OEM’s don’t go overboard with their cost-cutting measures. The only hardware relevant to the point I’m making is the SoC, which includes, among other things, the CPU and the GPU (for WP8 likely the Qualcom S4 Pro).

        Somewhat related to this, is the topic of fragmentation:

        > current handsets [WP7 devices] will not be able to run them [WP8 apps],
        > leading to a degree of fragmentation

        Wrong. Fragmentation doesn’t exist in the console market at all, even
        though we have the PS, the PS2 and the PS3 all in co-existence.
        Fragmentation occurs when developers are required to explicitly deal
        with software and/or hardware variability. At some point (that crops up
        very quickly) developers can no longer cope with variability (under the
        given economic constraints of their projects) which is when customers
        start noticing the problem, i.e. instability, compatibility and sub-par
        experience issues.

        Now to your issues:

        1) Do you seriously think these new devices will continue to run WP7 or 7.5?

        No. But I do hope MS will dictate that all WP8 devices must use the same Qualcom S4 SoC. That is exactly what they have done for WP7, and it is what many developers are hoping MS will do for WP8. This is where the rubber hits the road in terms of optimization potential. As soon as variability is introduced here, the “console model” goes out the window and fragmentation ensues.

        Lower-End devices are built by combining the same SoC with lower-end cameras, cheaper displays, batteries, cases or skimping on some capabilities completely (LTE for example).

        2) But why to talk of the future? such a thing is already happening.

        Yes, WP is already somewhat fragmented, but not all fragmentation is equal. Dealing with the fact that a gyroscope may or may not be available is absolutely trivial. It is almost not worth mentioning. Variability in peripheral hardware, even if it doesn’t exist at all, we can easily deal with. Making a graphics engine scale perfectly across varying GPU’s and CPU’s is a monstrous task in comparison… so monstrous, that nobody does it. Again: it is why nobody with a high-end PC graphics card is seeing anything close to what those GPU’s could actually do. It is why nobody with a high-end android phone is seeing anything close to what their devices could actually deliver. Ask for the same model (i.e. WP8 on WP7 hardware) and you are asking for the same mediocrity.

        3) ?
        I’m not really sure what your third point is. I agree that WP8 is not just about better hardware. I don’t agree that MS started on WP7 from scratch. Win CE, Zune (the UI we now call Metro), and Silverlight were al pre-existing technologies that got combined to make WP7. MS cut so many corners to improve their time to market that they are redoing a lot of all over again for WP8 (replacing Win CE, supporting the full .NET framework etc), which is one of the reasons it is taking so long.

        Anyway, if MS abondons the console model they currently have, they are also abandoning the benefits that come with it. That can can’t be changed, no matter how much MS works into WP8. We might not have to deal with the same UI skinning issues (does anybody like TouchWiz?), but other than that WP would need to start wrestling with exactly the same fragmentation issues as Android.

        • https://twitter.com/#!/HotmailAlias Hotmail Alias

          Thanks for your detailed explanation. Its enriching to learn from the wisdom of experts who can explain their knowledge in lucid and easily understandable words.

          I agree with your explanation of hardware differentiation on WP8 centering on SoC. I also agree that the console model is the better solution from a developer point of view, maybe even from the user satisfaction point of view. But the market realities that force developers to code for the lowest common denominator in a fragmented system, will also cause Microsoft to try including existing hardware for their future OS. Lets see how this pans out and if they can reach the moon that they are aiming for, with their version of Apollo.   

          • Collin5

            Thank you for taking the time to read the (much too) long posts and being open minded. Maybe you can incorporate some of those thoughts into one of your future articles.

            Just to be absolutely clear: I have no idea what MS will actually do
            either, but I do know that they had internal disputes over this as well… they decided not to discuss the issue in public, because it was deemed much too complicated. Just like in politics… when you find yourself explaining… you are loosing.

  • Pingback: Wenn WP8 erscheint, wird es uns dann als Update angeboten? Seite 24 - Windows Phone 7 Allgemein - Windows Phone Forum