


There are stuff like phoneGap (ok not the desktop part of your question) that says everything works on all phones but it does not benefit of the advantages of a plateform, it goes to the lower common denominator, meaning that your app is often less efficient than if made natively.Įven more hazardous, you inherit from bugs of these tools, and some can be really tricky to understand (is there a problem in my code, in phoneGap/xamarin ?) and you could loose much time on stuff like these.Įven Excel from Microsoft is different between OSX and Windows plateforms, they even fixed a bug in excel 2011 for mac, that is still present in windows versions ) (they have different business units if I remember correctly) a windows user and a mac user are not used to same interface, same application concepts, gestures on phones or trackpads, mac apps are generally not using the (F1,F2, etc. "UserFriendlyness" is a thing to take into account. Willing to do everything at once is nice (and often a cost question) but it is not a real option (unless cost is the major concern).Įven between iOS and OSX there are numerous differences, different concepts (option to have multiple windows on OSX / only one in iOS, different API even for common stuff, the "touch" of an iOS app will make you work differently, screen size will make you think of different functionalities or not all would fit in the iOS app). Honestly, I would go with creating an OSX app, iOS app and Windows app separately. NET) but you will still need a mac to compile the iOS / OSX versions, an iPhone/iPad/iPod touch to test on device, etc. It's possible (and brand new) through Visual Studio and Mono (as far as I understood it is an open source implementation of.
