Re: Apple and Cocoa (why don't they eat their own dog food?)
Re: Apple and Cocoa (why don't they eat their own dog food?)
- Subject: Re: Apple and Cocoa (why don't they eat their own dog food?)
- From: Bruce Veazie <email@hidden>
- Date: Sun, 12 Jan 2003 19:43:43 -0500
From: James DiPalma <email@hidden>
...
Apple used to promote Cocoa's ability to preserve consistency and
adapt to new functionality when
Apple updated Cocoa; if developers go about rolling our own windows
and widgets, Cocoa suffers.
...
Instead, follow the user interface guidelines for YOUR CUSTOMERS! Make
it easier on them to understand your programs. Easier for them to
identify common features, and to be able to handle common commands. And
hopefully easier for them to purchase your software.
Steve Sheets
Amen, Steve.
I've programmed in Windows for many years, using both Microsoft and
Borland libraries. IMHO, both companies' examples consistenty and
pretty thoroughly demonstrated how to implement standard interface
items.
However, I finally got tired of crashes, lockups and the Blue Screen of
Death. I bought my first Apple product, an iMac, just last September,
to try the more stable Unix underpinnings. I'm thrilled that an entire
development suite is provided with the package. I've upgraded to 10.2.3
and the Dec 2002 devtools.
However, I do not find the consistency in application interface (with
Apple's dev examples and products - iTunes, AppleWorks, iPhoto - or
with non-Apple products) that exists with most dev kits and products
for Windows. Toolbars and the effect of the toolbar buttons seems to
vary widely from app to app. Even in things simpler than UI controls,
like the use of Ctrl-right arrow and Cmd-right arrow, varies in effect
from product to product, both Apple and non-Apple. That increases the
steepness of the learning curve and frustrates users. I cringe whenever
I see (frequent) posts to this list asking "How do I get this-or-that
control to do <fill in your own 'I've got a better idea'>?"
Consistency in the UI develops the user's intuition. When his/her
intuition is right, the app becomes easy to use.
If your app isn't intuitive and easy for the user, it's a bad app.
Bruce J. Veazie
email@hidden
http://veazie.org
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.