I would like to argue in favour of %u201Cnative%u201D [1]. At least in
the regular case: messing around with my motoric memory, my system's
default shortcuts, my system's standard widget
look/behaviour/positions etc. is not likely to earn you good credits
;-) And, as frequently in design, it is det
I think it is more important to keep the core functionality and the
process of using the application the same on all platforms.
I use Evernote both on Windows, OS X, iPhone and Web, and what really
annoys me is that it behaves differently. When creating a new note,
the windows version automaticall
Matt,
I think what you are describing here has a lot to do with
expectations. As a Mac user, I expect an application that I install
and run locally to look and behave like a standard Mac app following
Mac OS conventions. When I use an app that has been poorly ported from
a Windows version
Hi Matt,
Take eclipse (www.eclipse.org) example, they have the native look and
feel at every platform, but at the same time, keep the interaction
(behavior) as uniform as possible, which definitly help it's user
experience.
But the key here, is
1, first the user experience is uniform
2. second, th
Hi,
Color me confused. What exactly do you mean by native? Do you mean
you've designed a different interface for each platform (which is
what I usually understand native to mean in this context) or do you
mean that you're designing a single interface for all 3 that is
native to some unspoken
Hi everyone,
We are charged with the redesign of a cross platform (Windows, Mac and
Linux) application. From data we've collected, we know about 93
percent of users are Windows users, 6-7 percent are Mac and the
remaining 1 percent are some flavor of Linux.
The application was originally written
