Solutions from Brainstorming
For this task, I sat down with a partner and we took turns saying ideas for how the alarm setting system might work and look. For this brainstorm, we focused on what kind of data needs to be entered.
Alarms can be set by location, so the device needs a way to add a location.
- Street map
- Map of Galaxy
- Shortcut for current location
- Parsecs (whatever those are)
- Street address
- Star System
- XYZ coordinates
- Planet Latitude/Longitude
- Point in orbit
- Vague, fuzzy description
- Presets for commonly visited places
On evaluation, it seemed that some universal way of defining a location would be needed, but having local options would be potentially useful to quickly set a location based on current context. For example, Earth-based street addresses might be useless on the Doctor’s home planet – I’m not sure if his planet even has streets – they are certainly useful when he’s on Earth. Saved locations would be especially useful if they’ll be used more than once.
Since the Doctor travels through time, the settings for alarm times will need to be more detailed.
Ideas for time inputs:
- Phase of moon
- Galactic epoch
- Astronomical time
- Orbit timing
- Year, month, day, etc
- Number of seconds since Big Bang
- Number of seconds from now
- Time until some event
- Harmonic convergence
- Time of a planet location
- When two or more planetary bodies converge
- During retrograde events
- Moon is in the 7th house
- Half-life of some radioisotope like carbon-14
- Speed of light
- Time light takes to reach home planet from star
- Home planet time (days, years, etc)
On evaluation, it seems like beings as advanced as the Doctor would have their own universal time units. The decaying radioisotope approach seems especially reasonable and accurate. Once again, when traveling, some way of entering a locally used time would be useful to avoid having to mentally convert between universal time and local time.
How Does the Alarm ‘Go Off’?
Finally, an advanced alarm like this one seems to need more features than a simple beep. Sometimes, any sort of sound at all might be dangerous. Here are the ideas we generated:
- Attach note to alarm
- Verbal message
- Keep quiet when in danger
- Send straight to brain
- Visual alarm
- Scrolling message
- Can be dismissed
- Password to dismiss
- Alarm that won’t go away until a condition is met
- Notifies somebody else if you don’t respond
- Starts pulling you toward something
- Engage homing device
- Put in a Panera order when you’re 10 minutes away
- Starts kettle of tea
- Activates another device
- Monitor heart rate to decide whether or not the Doctor is in danger
In discussion following this part of the brainstorming, we decided that the most important thing is that the alarm not put the Doctor in danger. The watch should intelligently handle this by itself, because it’s too easy to forget to put the watch in silent mode. (See pretty much every social situation in the early 21st century.) Next in importance, given all the different times and places for alarms, is the ability to tell the Doctor what they’re for. Some sort of short note explaining the alarm’s purpose would be useful. The alarm should be snoozable in case it can’t be dealt with at the time.
Solutions from Trigger-Based Brainstorming
A partner and I sat down and used the Trigger method. We each wrote down ideas for how the watch could indicate the direction of the TARDIS. Then, we swapped papers and expanded on each others’ best ideas.
Here are the ideas that seemed best:
- Project on the ground
- Route to follow
- Arrow pointing at TARDIS
- “pond rings” radiating from TARDIS
- 3D enhanced reality
- Show route emanating from user
- Show turns off in the distance
- Show a TARDIS icon on the horizon
- 3D flyover map
- Holographic Google Earth except the whole galaxy
- Like a planetarium
- Route and location of TARDIS in holograph
Human Interface Ideas
Given the complexity of data inputs and outputs, the display may need to be fairly complex. Entering data and displaying data will need to be carefully designed.
Display and interface ideas we found:
- Manipulate watch bezel to change settings
- Miniature planetarium display
- Project on wall
- Project directly onto retina
- Send sound directly to inner ear (inaudible to others)
- Project on ground, especially for homing
- Just the watch face
- Any nearby piece of glass like a car windshield
- Magnetism (gently pulls user in a direction)
- Hot and cold
- Voice directions
- Brainwave interface
- 3D holograph
- Watch hands move to point out directions
On evaluation, small features like watch faces won’t really be large enough for complex displays. Since the Doctor is a social creature, having the ability to share the display seems to rule out direct to eye/ear/brain methods, especially when dealing with less advanced species. Projected or 3D displays seemed to us to be the most shareable.
For the alarms interface, the idea of a 3D spherical display projected above the watch seemed to make sense, especially in light of needing to set a location for an alarm in a 3D universe. Mapping a single sphere in two dimensions is a whole science unto itself. Finding a spherical planet among many using a two-dimensional representation seems like it would be very difficult. Planets would potentially be on top of each other. Also, with a display in thin air over the watch, I find myself gesturing at it with my right hand as if spinning a globe. Zooming could be either a spreading/pinching gesture, or a scooping/pushing/pulling gesture.
Going with the 3D approach, I tried to imagine how setting time and alarm notes would be done, since those are solved problems in 2D rectangular displays. Since the display is spherical, I’m imagining a ring-based interface wherein sets of related options, such as terrestrial year occupy one ring. The circular shape would fill up the sphere in two dimensions nicely. To move between option sets, the ring sets’ circle could be ‘flipped’ to show a new screen.