Researchers have developed a powerful new tool that allows programmers to engage with work on their mobile devices to help make productive use of time away from their workplace.
In a new study done in collaboration with Microsoft Research, the team of researchers created a prototype tool called Mercury that lets programmers continue working on their mobile devices if they need to leave their desktop, and pick up back when they return to their workstation. Currently, programmers often spend a substantial amount of time at their primary workstation to make productive use of their workdays.
Alex Williams, a University of Waterloo Faculty of Mathematics graduate student, led the study along with Harmanpreet Kaur, a PhD student at the University of Michigan, and Adam Fourney, Jaime Teevan, Ryen White and Shamsi Iqbal from Microsoft Research.
“Mercury uses principles of micro productivity to create mobile-friendly programming work,” said Williams, a PhD candidate in Waterloo’s David R. Cheriton School of Computer Science, who undertook the study during his internship at Microsoft Research. “As users go mobile, Mercury performs a real-time scan of their existing source code to automatically generate a queue of microtasks programmers can immediately engage with at their leisure. Upon returning to their workstation, Mercury would have integrated the changes from the microtasks completed on-the-go.”
In developing the prototype, the researchers conducted two studies to understand how programmers currently use their mobile devices for work and what else they want to be able to do. The first study was a contextual inquiry with 10 software engineers. They used the findings from the observational phase to develop a survey which was employed to canvass 78 software engineers.
The findings from the contextual inquiry and online survey motivated Mercury’s design, which was then evaluated through a user study with 20 participants.
“We found that in addition to helping programmers continue their work on the go, a mobile work experience designed around micro productivity can also instil comfort in pausing work unexpectedly,” Williams said. “Programmers felt they could make meaningful progress in their work with Mercury’s micro-tasking experience in scenarios ranging from brief moments of downtime to the daily commute.
“It was also discovered that the longer someone is away from a project, the longer it takes them to get back into it mentally. Mercury can solve the problem of resumption as on average; we saw 18 of our 20 participants use something generated with the mobile tool while they were away from their desktop within seven seconds of getting back.”
Mercury is a prototype tool developed as a means to explore a new frontier of programming that takes place beyond the workstation. While the tool is not publicly available as a Microsoft product, Mercury’s success signals a new wave of tools designed to empower programmers’ ability to engage with their work without infringing on valuable personal time spent away from the workplace.
The study, titled Mercury: Empowering Programmers’ Mobile Work Practices with Microproductivity, authored by Williams, Kaur, Fourney, Teevan, White and Iqbal, will be presented at the ACM Symposium on User Interface Software and Technology to be held in New Orleans on Oct. 20-23.