Re: Application Design
Re: Application Design
- Subject: Re: Application Design
- From: Jon Hull <email@hidden>
- Date: Mon, 2 Jul 2007 16:00:52 -0700
The trick is to iterate the design. You want to have a clear idea of
what you are trying to do (and a rough interface) before you start
coding... but they are not really phases which can be separated. The
best programs iterate the design, testing and tweaking the design as
the application becomes more functional.
That being said, the worst possible thing you could do is write a lot
of code before designing the interface... you tend to lock yourself
into a design that way. Worse, that design is tied closely to the
internal structure of the program, and the "pipes start to poke
through the wall". A good interface is like a good magic trick, and
when the pipes show, it ruins the illusion.
I work as an interaction designer, and the most frustrating thing is
when a client comes to you with a product already in beta... and they
say "now make the interface work". At that point, all you can do is
apply the interaction equivalent of makeup, and start working with
them to fix the interface in version 2.0.
Thanks,
Jon
On Jun 30, 2007, at 11:00 PM, Rick Langschultz wrote:
Hey everyone,
Just wondering; when designing software do you first write the
code, or design the interface?
Just a question.
Rick
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden