Log In
Or create an account -> 
Imperial Library
  • Home
  • About
  • News
  • Upload
  • Forum
  • Help
  • Login/SignUp

Index
Calm Technology: Principles and Patterns for Non-Intrusive Design Praise Preface
Who Should Read This Book How This Book Is Organized Safari® Books Online How to Contact Us Acknowledgments
1. Designing for the Next 50 Billion Devices
Four Waves of Computing
The World Is Not a Desktop The Growing Ephemerality of Hardware The Social Network of 50 Billion Things
The Next 50 Billion Devices
Limit Bandwidth Usage Dedicate Separate Channels for Different Kinds of Technology Use Lower-Level Languages for Mission-Critical SystemS Create More Local Networks Distributed and Individual Computing Interoperability Human Backup
The Future of Technology Conclusions
2. Principles of Calm Technology
The Limited Bandwidth of Our Attention Principles of Calm Technology
I. Technology Should Require the Smallest Possible Amount of Attention II. Technology Should Inform and Create Calm III. Technology Should Make Use of the Periphery
Attention models Attention graphs
IV. Technology Should Amplify the Best of Technology and the Best of Humanity V. Technology Can Communicate, But Doesn’t Need to Speak VI. Technology Should Work Even When It Fails VII. The Right Amount of Technology Is the Minimum Needed to Solve the Problem VIII. Technology Should Respect Social Norms
Conclusions
3. Calm Communication Patterns
Status Indicators
Visual Status Indicators Status Tones Haptic Alerts Status Shouts
Ambient Awareness Contextual Notifications Persuasive Technology Conclusions
4. Exercises in Calm Technology
A Calm Interaction Evaluation Tool Exercises
Exercise 1: A Calmer Alarm Clock
Part A
Key considerations
Part B
Exercise 2: A Clock That Starts the Day
Part A Part B
Exercise 3: A Year-Long Battery
Part A Part B
Exercise 4: A Calmer Kitchen Exercise 5: A Fridge for Healthier Eating Exercise 6: Using Ambient Awareness Exercise 7: Bringing Haptics into Play
Conclusions
5. Calm Technology in Your Organization
Building Teams for Calm Technology
The Rule of Five Test Your Team Hire Differently from You Find Political Buffers
Design for Privacy
The User Experience of Privacy Get a Privacy Policy Anticipate and Expect Security Breaches
Selling Calm Technology to Managers
Objection 1: More Features Are Better
Solution
Objection 2: All of the Legacy Features Must Stay
Solution
Objection 3: What About All the Other Stakeholders?
Solution
Objection 4: There’s No Time for User Testing
Solution
Objection 5: The Product Must Stay Secret Until Launch
Solution
Entering a Product into Human Society: A Calm Product Launch
Refine Competition Do the Research! Allow Time for Real-World Testing Don’t Redesign the Entire Thing at Once Design for Human–Human Interaction Design for Optimum Battery Life
Conclusions
6. The History and Future of Calm Technology
Videoconferencing Before Skype The Beginnings of Calm Technology
A. About the Author Index About the Author Colophon Copyright
  • ← Prev
  • Back
  • Next →
  • ← Prev
  • Back
  • Next →

Chief Librarian: Las Zenow <zenow@riseup.net>
Fork the source code from gitlab
.

This is a mirror of the Tor onion service:
http://kx5thpx2olielkihfyo4jgjqfb7zx7wxr3sd4xzt26ochei4m6f7tayd.onion