Week 11
March 30, 2006
With generative session complete, discussions begin to center around identifying practical technological solutions for needs that have been addressed.
Team discusses using UMPC (ultra mobile personal computer) as the platform for our device. Team reviews Microsoft and Intel’s review of this technology.
http://www.intel.com/design/mobile/platform/flash/umpc/
http://www.intel.com/design/mobile/platform/umpc.htm
http://www.microsoft.com/windowsxp/umpc/mobile.mspx
http://www.microsoft.com/windowsxp/umpc/work.mspx
http://www.microsoft.com/windowsxp/umpc/hardware.mspx
http://msdn.microsoft.com/mobility/tabletpc/umpc/
March 31, 2006
Suggested list of interactions that need to be addressed in the wireframe screens of our device is discussed. We plan to meet Sunday to compare what each of us has come up with.
Key interactions that need to be addressed in the design include:
Explicit Query
Our system needs to allow direct requests for information.
Send/Receive Messages
Mark should be able to send a get messages in a variety of ways, such as voice, video and text. The designs should imagine how these might work together and the support the varied types of messages.
Mapping
Geographically navigating is a big component of our system. What do these maps look like? How do you pull one up and manipulate it?
Dashboard
This is the idea of there being a single screen that shows Mark everything the system “thinks” he wants to know about right now.
Alerts
Various activities require Mark to be alerted—or not alerted. How does the system know when to alert them and how?
Calendar/Scheduling
The system will need to know something about Mark’s schedule if it wishes to deliver a contextual and personalized experience.
Common themes
There are some common concerns that run through the entire system: contextual hierarchy, configuration, privacy, and reusable interface widgets.
Comments