Friday, March 11, 2016

Redesigning the Apple Watch UI

http://www.lukew.com/ff/entry.asp?1951#menu

The vast majority of my interactions with the Apple Watch involve notifications. I get a light tap on my wrist, raise my arm, and get a bit of useful information. This awareness of what's happening helps me stay connected to the real World and is the primary reason I enjoy wearing a smartwatch.
use case for smartwatches: awareness
Thanks to "long look" notifications, I'm also able to take action on some notifications —mostly to triage things quickly. Much more rarely do I engage with Glances and even less with apps. This creates a hierarchy of use: notifications, glances, apps.
priorities when designing for apple watch

Thursday, March 10, 2016

The 10 skills you need to thrive in the Fourth Industrial Revolution

http://www.weforum.org/agenda/2016/01/the-10-skills-you-need-to-thrive-in-the-fourth-industrial-revolution?utm_content=bufferb01ee&utm_medium=social&utm_source=facebook.com&utm_campaign=buffer

Five years from now, over one-third of skills (35%) that are considered important in today’s workforce will have changed.
By 2020, the Fourth Industrial Revolution will have brought us advanced robotics and autonomous transport, artificial intelligence and machine learning, advanced materials, biotechnology and genomics.
These developments will transform the way we live, and the way we work. Some jobs will disappear, others will grow and jobs that don’t even exist today will become commonplace. What is certain is that the future workforce will need to align its skillset to keep pace.
A new Forum report, The Future of Jobs, looks at the employment, skills and workforce strategy for the future.

The report asked chief human resources and strategy officers from leading global employers what the current shifts mean, specifically for employment, skills and recruitment across industries and geographies.

Monday, November 9, 2015

Assignments by 11/10

1. Revised Research Presentation (update VISUALLY) and add more researches if you need.

2. Create a suggested Flowchart (save as PDF and bring in class printed version)

3. Paper Prototype:
  • 10-15 screens (wireframe: computer or pen, text should be readable on your sketch)
  • Taking photos: a process of your group discussion. 
  • Bring actual "individual paper Prototype" in class. 
*Discussing App names.

Posting all into Google Drive