To read all comments associated with this story, please click here.
Anything other than the user interface code can be shared, but essentially nobody writes 100% pure MVC code, which means there's a lot of places where things need to be changed when porting from Cocoa to Cocoa Touch. A Foundation-only library can be shared if you've got some unique networking or data processing code, but for a lot of apps, the UI defines and deeply affects the whole structure of the application.
There are issues on Windows Phone 7 with certain base classes not being provided - sockets being a notable example - which can cause complications, but generally if you write to WP7's requirements it'll be easier to share code with a Silverlight app than it is to share between iOS and OS X.
I can't see how this could be possible, regardless of platform or tools.
I simply can't see how one could express a UI in terms that could properly scale up to 1920*1200 or down to 640*320 resolutions. Non-GUI code for OS X is actually pretty close to iOS code (as in extremely close, barring any APIs that are not available on both platforms).
If Microsoft's AppX provides the same level of code sharing, it would be great for developers. If they do find a way to make porting UI code with minimal effort possible, I will be pleasantly surprised.
maybe you were confusing applications that were build for iPhone automatically resizing to the iPad. Both of those are on iOS though. Developing "cross-Mac-OS" is far from easy and Apple isn't really interested (yet) in making it easier.
In their opinion everyone should have an iPod for music, an iPad for browsing and playing games on fixed locations, an iPhone for communicating on mobile locations and of course a full blown Mac for doing all of those things and maybe even creating something at home or in the office. All of these devices have different goals, so software only has to be accessible on 1 of them?
Windows Phone 7 apps can share much more of their codebase with desktop OSes (Windows *and* Mac) via Silverlight. So Microsoft is already ahead in this area, and providing a common app distribution format will put them firmly in the lead.
Did you actually read what you quoted or did you just choose a random quote to plonk at the top as to make it appear as though you read the article and Thom's take on the matter? the quote is as follows with the part in bold that you should have focused in on:
What part of 'similar' don't you understand? similar means 'close enough' or 'near to it' or 'not exactly like it'. The appx idea is very similar to what Apple has be it Microsoft making fully portable from top to bottom rather than requiring the front end to be re-written again for a new form factor.





Member since:
2006-08-29
That's one fine incentive for developers - write your application, and have it scale from phones to tablets to desktops. Apple already offers something similar, of course, so Microsoft is a tad bit late to the game.
They do? I must have missed a big announcement. Last I checked, you got to write your app once for OS X, and then rewrite the whole UI for iOS using a different framework. Sure, there's a third-party framework in development that will let you use iOS's UIKit APIs on OS X, but even that's not a complete solution, and it's not something offered by Apple.
Windows Phone 7 apps can share much more of their codebase with desktop OSes (Windows *and* Mac) via Silverlight. So Microsoft is already ahead in this area, and providing a common app distribution format will put them firmly in the lead.