Differences between revisions 2 and 3
Revision 2 as of 2011-05-05 00:52:56
Size: 946
Editor: shoobe01
Comment:
Revision 3 as of 2011-05-05 02:09:33
Size: 1699
Editor: shoobe01
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Like interactive design, if this book was all things to all people, it would be much larger -- or we'd simply never have finished it. Our focus here has been on design. By which we mean information architecture, information-, interaction-, interface-, and visual design, and content. Like interactive design, if this book was all things to all people, it would be much larger -- or we'd simply never have finished it. Our focus here has been on design. By which we mean information architecture, information-, interaction-, interface-, and visual design, and copywriters.
Line 3: Line 3:
If your job title, job description or deliverables have names like those, and you work in mobile, then you need this book. If your job title, job description or deliverables have names like those, and you work in mobile, then you need this book. If you are moving from another field, such as mobile design, or are switching from one narrowly focused mobile area to another, this book encompasses general patterns that HELP>>>
Line 5: Line 5:
If you work in a related field, If you work in a related job, there is still something for you. Human factors engineers and HCI experts will find numerous discussions of why these solutions have become patterns, and references to cognitive psychology and physiology reasons these are true.

Development is not addressed as such, but the book has been organized so it can be used to find specific solutions to any mobile interaction. If you don't have a dedicated design team, you can use the patterns to find and focus on solutions, confirm they are technically possible, and to avoid common implementation pitfalls.
Line 8: Line 10:
SOMETHING>>>>

Like interactive design, if this book was all things to all people, it would be much larger -- or we'd simply never have finished it. Our focus here has been on design. By which we mean information architecture, information-, interaction-, interface-, and visual design, and copywriters.

If your job title, job description or deliverables have names like those, and you work in mobile, then you need this book. If you are moving from another field, such as mobile design, or are switching from one narrowly focused mobile area to another, this book encompasses general patterns that HELP>>>

If you work in a related job, there is still something for you. Human factors engineers and HCI experts will find numerous discussions of why these solutions have become patterns, and references to cognitive psychology and physiology reasons these are true.

Development is not addressed as such, but the book has been organized so it can be used to find specific solutions to any mobile interaction. If you don't have a dedicated design team, you can use the patterns to find and focus on solutions, confirm they are technically possible, and to avoid common implementation pitfalls.

SOMETHING>>>> Even if you have been doing the job for years, it changes all the time,

XXXXXXXXXXXX

Ideally, hardware designers also.

But they never will, so anyone who designs for mobiles of any sort. Full of design patterns for the interactive space, but also hardware hints and related topics.

Which are there because often to make the best, most contextually-relevant user interface, you need to understand glare and reflectivity and the impact of buttons being in different places...

Who This Book Is For (last edited 2013-04-08 20:01:02 by shoobe01)