TYME
iOS utility application
/skills
interaction design, data visualisation, ios development
thought, designed, and built using
ASSUMPTIONS + RESEARCH
i began with some assumptions and personal experiences to understand any biases. while learning about my own experiences, i wanted to explore what kind of questions i'm asking and what kind of answers i seek when converting time zones.
figjam––understanding assumptions (purple), relevant research questions (yellow), and natural interaction patterns (white)
to understand how other's perceive this process, i worked with 5 participants during a co-design workshop. here, i focused on the frequency, reasons, and thoughts when converting time zones. for 3 scenarios, participants would mentally walk me through their process of converting time zones and for the other 3, they would actually perform the task. in between these, they were also probed to visualise a diagram of what they think when converting time zones (right).
co-design workshop analysis
time zone conversion visualisations from co-design participants
interestingly, participants were visualising time zones on a scale. passage of time was like a flow to them. most participants were thinking in contexts of day vs. night.
CURRENT SYSTEMS
simultaneously, i was auditing current systems.
enterprise systems like outlook are for paid teams, require technical load, and do not work for ICs.
platforms like lettucemeet/doodle are slow, labour intensive, and require negotiation.
TYME SOLVES FOR THIS
there are 3 steps to it–
get on the app.
add location(s).
decide
