Linked by Thom Holwerda on Fri 1st Feb 2013 18:25 UTC
Windows A few days ago, Microsoft released the long-awaited Windows Phone 7.8 update for all those users who will be stuck on Windows Phone 7 forever because there's no upgrade path to Windows Phone 8 other than buying a new phone. Now that it's here, what, exactly, does WP7.8 to the table?
Thread beginning with comment 551235
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by Nelson
by bentoo on Sat 2nd Feb 2013 16:49 UTC in reply to "RE[3]: Comment by Nelson"
bentoo
Member since:
2012-09-21

Windows Phone is fragmented on platform level - WP7 and WP8.

Handling API fragmentation is much easier than platform fragmentation.


This is only a problem for the older (WP7) device. Just the same as an Android application that has a minimum API level of 14 is not going to run on a Gingerbread device.

Reply Parent Score: 3

RE[5]: Comment by Nelson
by cdude on Sun 3rd Feb 2013 12:59 in reply to "RE[4]: Comment by Nelson"
cdude Member since:
2008-09-21

In which case the developer made the decision not to support API-level <14 cause eg the app/widget/service needs features that are only available in >13. Point is that decision is up to the dev. If the dev likes to support <14 then there is no reason to not AND all newer versions are supported out of the box.

Edited 2013-02-03 13:03 UTC

Reply Parent Score: 2

RE[6]: Comment by Nelson
by darknexus on Sun 3rd Feb 2013 23:32 in reply to "RE[5]: Comment by Nelson"
darknexus Member since:
2008-07-15

Nice theory, but it doesn't always work that way if either the API changes or an OEM does something odd to parts of their phone (Samsung, I'm looking at you). In these situations, an update is still needed. The app will only run on newer versions of the API so long as the API functions the app relies upon remain unchanged. You don't get support by default when changes occur.

Reply Parent Score: 3