Skip to main content
  1. Blog
  2. Article

May’s reading list


Here are the best links shared by the design team over the last month:

  1. MyData 2016 Conference
  2. Next-level collaboration: the future of content and design
  3. Collection of popular UX flows
  4. Microsoft’s hover gestures for Windows phones are magnificent
  5. What Happened to Google Maps? Surprising Changes to Google Maps’s Cartography
  6. 7 Things Every Designer Needs to Know About Accessibility
  7. Meaningful CSS: Style Like You Mean It
  8. Bicycles Built Based On People’s Attempts to Draw Them From Memory
  9. Learn From the Past, Enhance for the Future
  10. Atomic Docs. A styleguide generator and component manager
  11. How Technology Hijacks People’s Minds — from a Magician and Google’s Design Ethicist
  12. Star Wars Episode IV in one picture
  13. Airbnb Design: Building a Visual Language
  14. Dribbble Comment Generator
  15. Confident, Instinct, and Knowing When to Fight Back: An Interview with Canonical CEO Jane Silber

Thank you to Alejandra, Ant, Carla, James, Jamie, Joe, Jouni, Peter and me for the links this month!


Related posts

What designers should know about semiotics

What happens when you look at an apple? When you see it, you perceive the apple and assign meaning to it based on your language, experience, and personal preferences – such as...

Challenges designers face in open source (and how to fix them)

Open source powers up to 90% of modern software, yet many projects lack usability. Canonical’s Design team surveyed 115 cross-functional professionals to uncover the 4 core...

Template: Streamlining open source design contributions

As designers working at Canonical, we’re always thinking about open source. We believe that encouraging more designers to contribute to open source benefits everyone, from the...

Decoding design: How design and engineering thrive together in open source

Open source thrives on engineering-driven processes. Fast feedback loops, terminal tools, Git workflows: they’re the lifeblood of how we build software in the open. But for...