Interact 2017: ReRide demo and more

Indian Institute of Technology Bombay, 25–29th September 2017

Gaurav Singh
Srishti Labs
5 min readSep 30, 2017

--

I’m beginning to write this as we complete the first day of ReRide demonstration at Interact 2017 Conference in IIT Bombay. The last week till afternoon today have been quite intense for us but also has been quite fruitful. It was very gratifying to finally see the synergy of the team to complete the demo despite few challenges we faced. The demo intended to develop a working proof of concept to demonstrate the intent, which we think has met, though the time crunch has affected us and we could not do the pilot test in a real setting. Nevertheless, we were ready for the Demo!

The entire exercise just echoed what I already believe. There is a lot of value in making physical and working concepts (esp. for designers), more often you’ll find that you’re rethinking most of your design decisions made when drafting ideas. What you see is “not” what you get!

One of the things that I think is quite instrumental for designers is the ability to think spontaneously — and use the brute-force approach. It is not always possible to come with solutions that are guaranteed to work in real settings.

The Media Lab’s founding director, Nicholas Negroponte, famously said ‘demo or die,’ as opposed to publish or perish, the tradition academic way of thinking, Ito told the TED audience in March (2014). “The demo only has to work once because the primary mode of us impacting the world was through large companies being inspired by us and creating things like the Kindle or Lego Mindstorms. But today, with the ability of to deploy things into the real world at low cost, I’m changing the motto now. And this is official: deploy or die.” […] “Less planning and more presence in the moment can accelerate innovation, he argues. Getting objects out into the real world is the point. Don’t be a futurist, he urges, be a now-ist.”

Photographs of putting together the ReRide demo prototype for Interact Conference.

Our prototype included — a) Seat cover with sensors embedded to get information about rider’s balance, b) a wearable sensor to sense how much rider lean in, c) a mobile/dashboard display, d) a push button near the left handle. These components together sense rider’s posture and present an abstract visualization to the rider during or post ride.

Left: ReRide Demo space for Interact 2017 at Victor Menezes Convention Center, IIT Bombay, Right: Mangesh Ashrit and Somya Saxena explaining through prototype at the ReRide demo space. Link to Paper: https://link.springer.com/chapter/10.1007/978-3-319-68059-0_43

Global Thoughts: Local Designs In this new age of global connectivity, designers are often required to design products for users who are beyond their borders and belonging to distinctly different cultures. The process of designing products is becoming more multi-disciplinary by the day. Solutions are now designed with a global perspective in mind, however local the solution might be. For those in the field of human-computer interaction, the phenomenon of global thoughts, local designs would have a direct impact. It encompasses the areas of HCI in the industry of emerging economies, HCI contributions in socio-economic development, HCI for products and services in emerging markets, including mobile systems, HCI and designs for low-literacy users, HCI and designs for bottom of the pyramid users, and HCI for remote contexts, including issues related to international outsourcing / global software development. We would develop onthese ideas going forward. (From www.interact2017.org)

Dr.Naveen Bagalkot presenting a short paper on “Watching your Back while riding your bike” co-authored with Dr.Tomas Sokoler (Photo by Mangesh Ashrit) Link to Paper: https://link.springer.com/chapter/10.1007/978–3–319–67684–5_19
Closing keynote speech by Matt Jones

Key Points

  • How do we decide and fix the technology stack for the prototype, when the prototype is evolving? Working on the same stack will be easier and convenient for teams but less flexible. And the changing stack could be more flexible to achieve the goals, but not easy for the team.
  • Sketch vs Prototype? Identifying objective and scope of demonstration to really leverage on the feedback.

Sketches dominate the early ideation stages, whereas prototypes are more concentrated at the later stages where things are converging within the design funnel. Much of this has to do with how they differ with respect to the attributes of cost, timeliness, quantity, and disposability that we discussed above as characterizing sketches. (From Sketching User Experiences by Bill Buxton)

  • I think the most challenging part in making demo-able prototypes is the integration (of various parts inside the prototype and how they interact with each other). What I think happens (at least with us) is that we spend generous amounts of time in thinking and making individual components and do not anticipate what it means to integrate these several elements.

Our Team: Dr.Naveen Bagalkot, Dr.Tomas Sokoler, Riyaz Shaikh, Gaurav Singh, Anders Edelbo Lillie, Vignesh Chakravarthy, Pratiksha Dixit, Sapna Nayak, Mangesh Ashrit, Somya Saxena, Ashwin Senthil Kumar, and Aditi Rai.

Also special thanks to Pranjal Jain for his help putting up the demo at the site.

Congratulations to Pratiksha Dixit and Devarani Bodanapu for taking part and shortlisted as finalists in Pitney Bowes Design Challenge at Interact 2017 conference.

--

--

Gaurav Singh
Srishti Labs

Building @mathscapes , Helping students with design+tech @srishtiartdes and copiloting @topcoder