What makes a Mac App?
Written by Chris Tangora
A little off topic, but an interesting thought ...Recently I was filling out a form trying to convince a non-Mac developer to port their software to the Mac platform and they had the question, "In your own words, what differentiates a Mac product from a Windows product?"
Good question. In theory they both do the same thing, they would both do the same function (i.e. edit/arrange photos, music, movies, create 3D animation, architectural drawings, etc). But I thought it would be a good question to throw out to a Mac-loving crowd ...
In your own words, what differentiates a Mac product from a Windows product?
Set as favorite
Bookmark
Email this
Hits: 1455
Trackback(0)
TrackBack URI for this entry
Comments (6)
Show/hide comments
#1 System Stability, #2 System Isolation (If a program crashes, it doesn't take the whole system with it), #3 Interface. It is as simple or as complex as you wish it to be.
-
- +0
-
-
What other platform could generate a Gallic site such as MacBidouille? There is something about a Mac, unlikely as it may seem, that draws forth the Systeme D itch: to modify this side of desecration.
-
- +0
-
-
When asking the question, one must also look at what framework was used to make the Mac app. If Cocoa is used, then the application inherits all kinds of tight integration into the OS and other applications. If Carbon is used, some of that integration is lost, and if Java is used, even more is lost. The elegance of the interface also decreases the further you move away from Cocoa. Pure Cocoa apps, if designed well, feel amazing to use. There's only ever been one program that I've actually enjoyed using on a Windows computer, and that was Microsoft Publisher, of all things. It felt good, as good as a Windows program can feel.
-
- +0
-
-
It's the ease of use for me; trying to use office 2008 on the new macs remind me of the simplicity of iWork. Keynote beats powerpoint any day!!!
-
- +0
-
-
Write comment
