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 551243
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by Nelson
by Nelson on Sat 2nd Feb 2013 20:10 UTC 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

RE[6]: Comment by Nelson
by Nelson on Mon 4th Feb 2013 14:06 in reply to "RE[5]: Comment by Nelson"
Nelson Member since:
2005-11-29

I think its purely artificial, and API/Platform fragmentations aren't really so different.

In fact API level fragmentation is just a narrower way to view platform fragmentation as a whole.

The Android API levels are implicit with the platform version, you won't have the same version supporting two differing API sets. The same is true of Windows Phone, though the fragmentation is much, much more limited in impact.

Microsoft's pain in this area is purely self inflicted and speaks to a lack of convenience to the developer more than it says anything about platform fragmentation.

Overtime I'm certain they will solve it, they always do, but time isn't really in abundance when you're behind in the first place. These things needed to be happening yesterday.

Reply Parent Score: 3