|
Size: 1771
Comment:
|
Size: 2939
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Like any good interactive design, a specific scope has been kept in mind from the very beginning -- 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. | [[http://www.amazon.com/gp/product/1449394639/ref=as_li_tf_tl?ie=UTF8&tag=4ourthmobile-20&linkCode=as2&camp=217145&creative=399373&creativeASIN=1449394639|{{attachment:wiki-banner-book.png|Click here to buy from Amazon.|align="right"}}]] |
| 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 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>>> | As with any good form of interactive design, we have kept a specific scope in mind from the moment we started writing this book. If this book was intended to be 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 this we mean information architecture; information, interaction, interface, and visual design; and copywriting. |
| Line 5: | Line 5: |
| 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. | If your job title, job description, or deliverables have names like those just mentioned, and you work in mobile, you need this book. Whether you are working on apps or websites for mobile (or any of many other things), this book addresses the common underlying principles in order to help you make better decisions and understand how to create better designs. |
| Line 7: | Line 7: |
| 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. | If you are moving from another field, such as desktop web design, or are switching from one narrowly focused mobile area to another, this book encompasses general patterns that can help you understand how to move from one type of device or one type of interaction to another. |
| Line 9: | Line 9: |
| If you work in a related job, this book still has something for you. Human factors engineers and HCI experts will find numerous discussions of why these solutions have become pat- terns, and references to cognitive psychology and physiology reasons these are true. | |
| Line 10: | Line 11: |
| SOMETHING>>>> Even if you have been doing the job for years, it changes all the time, |
Development is not addressed as such, but the book is organized so that you can use it to find specific solutions to any form of 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 avoid common implementation pitfalls. |
| Line 13: | Line 13: |
| Hardware designers, or anyone who can influence hardware design, will find specific guidelines to best practices in interactive, such as key labels and the use of sensors. Though these are included primarily for use by interaction designers—to understand how the hardware influences their on-screen behaviors—they are also specific enough to be used for design of the interactive portions of the hardware itself. | |
| Line 14: | Line 15: |
| ------- Next: [[What We Mean by “Mobile”]] ------- = Discuss & Add = Please do not change content above this line, as it's a perfect match with the printed book. Everything else you want to add goes down here. |
|
| Line 15: | Line 21: |
| XXXXXXXXXXXX | == Examples == If you want to add examples (and we occasionally do also) add them here. |
| Line 17: | Line 24: |
| 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... |
== Make a new section == Just like this. If, for example, you want to argue about the differences between, say, Tidwell's Vertical Stack, and our general concept of the List, then add a section to discuss. If we're successful, we'll get to make a new edition and will take all these discussions into account. |
As with any good form of interactive design, we have kept a specific scope in mind from the moment we started writing this book. If this book was intended to be 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 this we mean information architecture; information, interaction, interface, and visual design; and copywriting.
If your job title, job description, or deliverables have names like those just mentioned, and you work in mobile, you need this book. Whether you are working on apps or websites for mobile (or any of many other things), this book addresses the common underlying principles in order to help you make better decisions and understand how to create better designs.
If you are moving from another field, such as desktop web design, or are switching from one narrowly focused mobile area to another, this book encompasses general patterns that can help you understand how to move from one type of device or one type of interaction to another.
If you work in a related job, this book still has something for you. Human factors engineers and HCI experts will find numerous discussions of why these solutions have become pat- terns, and references to cognitive psychology and physiology reasons these are true.
Development is not addressed as such, but the book is organized so that you can use it to find specific solutions to any form of 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 avoid common implementation pitfalls.
Hardware designers, or anyone who can influence hardware design, will find specific guidelines to best practices in interactive, such as key labels and the use of sensors. Though these are included primarily for use by interaction designers—to understand how the hardware influences their on-screen behaviors—they are also specific enough to be used for design of the interactive portions of the hardware itself.
Next: What We Mean by “Mobile”
Discuss & Add
Please do not change content above this line, as it's a perfect match with the printed book. Everything else you want to add goes down here.
Examples
If you want to add examples (and we occasionally do also) add them here.
Make a new section
Just like this. If, for example, you want to argue about the differences between, say, Tidwell's Vertical Stack, and our general concept of the List, then add a section to discuss. If we're successful, we'll get to make a new edition and will take all these discussions into account.