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 551173
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by Nelson
by JAlexoid on Fri 1st Feb 2013 23:06 UTC in reply to "RE[2]: Comment by Nelson"
JAlexoid
Member since:
2009-05-19

I understand you pointing out the issue on the other platform, but it's off topic and not even relevant(2.3 > 4.x is a big upgrade for Android, it's Win200 > WinXP. WP7 > WP8 is not an upgrade it's mostly a different platform, it's Mac OS9 > OSX)

Android world has shown it can handle the API level fragmentation.
Windows Phone came with the promise of no fragmentation.
Android is fragmented on 2 levels - API and GPU.
Windows Phone is fragmented on platform level - WP7 and WP8.

Handling API fragmentation is much easier than platform fragmentation.

Reply Parent Score: 5

RE[4]: Comment by Nelson
by bentoo on Sat 2nd Feb 2013 16:49 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[4]: Comment by Nelson
by Nelson on Sat 2nd Feb 2013 20:10 in reply to "RE[3]: Comment by Nelson"
Nelson Member since:
2005-11-29


Android world has shown it can handle the API level fragmentation.
Windows Phone came with the promise of no fragmentation.
Android is fragmented on 2 levels - API and GPU.
Windows Phone is fragmented on platform level - WP7 and WP8.

Handling API fragmentation is much easier than platform fragmentation.


I think they're two ways of saying the same thing. Windows Phone 7 and Windows Phone 8 would actually have close to no fragmentation IF Microsoft would've made the decision to support one unified app project file.

The API differences are very, very minimal (in fact, this is one of my complaints actually.)

WP 7.0 to WP 7.5 was more fragmented than WP 7.5 to WP 8.0

Also FYI: You can access some APIs from a WP7 app using reflection and it works on WP 7.8 and WP8

Reply Parent Score: 4

RE[5]: Comment by Nelson
by JAlexoid on Mon 4th Feb 2013 12:45 in reply to "RE[4]: Comment by Nelson"
JAlexoid Member since:
2009-05-19

Like I said. It's not really an API fragmentation thing, it's a platform fragmentation thing.

Reply Parent Score: 3