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 551322
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Comment by Nelson
by JAlexoid on Mon 4th Feb 2013 12:45 UTC 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

RE[7]: Comment by Nelson
by JAlexoid on Mon 4th Feb 2013 14:53 in reply to "RE[6]: Comment by Nelson"
JAlexoid Member since:
2009-05-19

One big question that I might be missing - did they provide a native development kit with WP7.8?(The C++ one)

If they haven't, then there's the problem I'm referring to.

Reply Parent Score: 2

RE[7]: Comment by Nelson
by cdude on Mon 4th Feb 2013 15:32 in reply to "RE[6]: Comment by Nelson"
cdude Member since:
2008-09-21

The Android API levels are implicit with the platform version, you won't have the same version supporting two differing API sets.


And for you too: http://developer.android.com/guide/topics/manifest/uses-sdk-element...

"Android applications are generally forward-compatible with new versions of the Android platform."

The same is true of Windows Phone, though the fragmentation is much, much more limited in impact.


It is only true for Windows Phone where you need to port WP7 apps. http://news.softpedia.com/news/Port-Windows-Phone-Apps-to-Windows-8...

"A Windows Store app using C++, C#, or Visual Basic, using XAML, is the preferred model for ports from Windows Phone 7. If you are familiar with Silverlight, you can port to a Windows Store app using XAML by using familiar languages like C# or Visual Basic, and a similar set of UI elements and APIs"

Similar != same. Another: http://allaboutwindowsphone.com/flow/item/15847_Channel_9_ready_to_...

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.


Now we have WP7 apps, WP8 apps, Win8 apps, RT apps and end of this year Windows 9 Blue appears which is going to change that story once more. Again! Horrible fragmentation, deprecation and new API turnaround every year.

Edited 2013-02-04 15:39 UTC

Reply Parent Score: 1