Considering that I wrote that companies might think it's cheaper, I'm going to go with yes, I realize that companies might think it's cheaper.
Likewise, it's also cheaper for PC Manufacturers to sell me junk PCs loaded up with BloatWare, yet I buy Macs. Just as it's perfectly reasonable for company A to make a product that user B finds repellant, it's also perfectly reasonable for a company to make a Mac product that sucks, and it's equally reasonable for a Mac user to avoid it at all costs. Neither party is wrong in any sense, any more than WalMart is wrong for not selling full carbon mountain bikes or Ibis Cycles (a specialty manufacturer who lays their frames up by hand in the USA) is wrong for not rebranding a Chinese steel MTB at a $500 price point.
It's a plus for the users coming from the PC market because they don't have to relearn the interface.
This is not as sound an argument as the one we agree on. Replicating the PC experience with your Mac product works if you have all these PC users at the office and one day IT removes their PCs and replaces them with Macs. Or if you have a company with Macs and PCs and IT support costs show up in a report somewhere, but Mac user frustration with a poor interface is "off balance-sheet."
But if someone owns a PC and decides to switch to a Mac, it's because he explicitly doesn't like the PC experience. Replicate the PC experience on his Mac, and you may find that he switches products as well as computers.
I have Parallels. If you log into the Guest account on my machine and want to run Skype, I'd rather you use Skype for Windows and get exactly what you want than deal with something that is kinda-sorta Skype for Windows, but not enough to delight you as a user.
[citation needed]
edit: bring them on! :D
Is it? Can you cite some sources?
I'd less native UIs to take longer, as more custom widgets and chrome is requires. Not to mention, the result is more likely to "feel wrong" since it's less likely to conform to that platform's conventions.
From what I recall, Skype's Windows UI is actually written in Delphi - maybe that has changed now, but I think don't they actually have a unified code base for the user interface.
This of course doesn't mean that they shouldn't be doing so much more on both systems - I just think in this case the requirement of having a similar application on both systems is necessary.
A good cross-platform app isn't just dumbly copied at the whiteboard stage of MVC planning. It needs to have certain similarities, sure, but the key interface elements will integrate with the host operating system.
Since Windows has window-attached menu bars, why don't cross-platform apps on a Mac have the same thing? Don't say because there's a menubar object to attach commands to. I've seen plenty of apps that use nspopupbuttons to create window-attached menus while clearing the global menu. The reason it's not done is that it's egregiously bad taste. Defeating the user's expectation of how the app interacts with the operating system forces the user to break out of typical interaction into some unknown set by the developer. It's almost never a pleasant transition because someone with the ego to say "do it my way or else" generally doesn't care about testing on users.
In this case, Skype's mistake was breaking OS X's window management portion (Expose), along with the fact that mac applications are almost always one window : one task.
Certainly interoperability isn't an issue - the point is that it's in their best interest to maintain a common application interface. For example, I work at a company of 50 people and we have all variations of Mac, Windows and Linux machines running. By being able to support one interface internally it makes it a lot easier - as well as when certain users switch from their Windows machines in the office to their Mac's when working from home.
Whereas, it's easy to measure the amount of time IT spends supporting the product. So if there are two different UIs, it's easy to see that you need two different training sessions for users, but hard to measure how much time the Mac users lose struggling with the UI.
As I said, this is hardly a Mac/PC thing. You often see it in horribly designed internal applications. It's easy to measure the cost of development but hard to measure the productivity lost due to craptacular UX. So in 2011 I still see RFQs from clients asking for search pages where you fill in a complex form indicating which field you want searched and how to search it, instead of implementing a single full-text search across the application.
Why should an end user, who could use multiple platforms, need to understand two different layouts for the same program. This has nothing to do with different vendors, but the fact that a company needs to invest serious time in to developing a UI that is intuitive in all platforms they are targeting. The user experience should be well thought out so that it is a great application that takes advantage of the operating system interfaces that they are working with. If that user experience is lacking then someone dropped the ball - which is a burden for end users, IT folks and so forth.
This is the number one reason that I prefer Mac-only products to products that are available on both Windows and Mac.
Invariably, the companies decide that since they have 4x the sales on Windows as on Mac, the correct course of action is to build a product that is identical in almost every way with just a very thin GUI "skin" on the outside that is Mac or Windows specific. I don't know if this is because they think that the Windows sales "validate" the UX design or if it's an attempt to save money by having a single code base (or both?), but the results are invariably awful on the Mac.
Windows users are not interchangeable with Mac users. What "works" for someone who was given their PC by the IT department does not work for someone who deliberately chose to buy a product with a tiny market share.