Scan it. Say it. Shop it. hiku lives in your kitchen, scans barcodes and recognizes your voice – creating a shared shopping list on your phone so you always know what you need. It has one button simplicity so everyone in the family can use it to help keep the list up-to-date.
hiku also connects to online stores to make online shopping a breeze.
I started working on hiku on nights and weekends. When former colleague Rob Katcher reached out for help on his new startup I was eager to help. I had recently realized that I wanted to work on something I had a more personal connection to. I do a lot of grocery shopping and cooking and I was excited to get involved. I created the initial design for the hiku shopping list app and helped on the design of the overall hiku system. Months later, with version one of hiku on the market and a small seed round in the bank I joined full-time.
My first goal as the full-time head of product and design at hiku was to improve retention. When I started only 39% of users were active on a monthly basis after 6 months – clearly there were improvements to be made.
The bulk of my first month was spent in hiku user’s kitchens. We talked about how they grocery shop, life before hiku and what works and doesn’t work about hiku. I observed them using the hiku device and the hiku app. I took these observations and created a user-centric backlog of design and development tasks aimed at fixing fundamentals of the app and filling in “missing features” that consistently came up in conversation.
A user’s first experience with hiku is to connect it to their home wireless network and learn how to use hiku. The v1 hiku setup experience was a significant source of support tickets. I led the process of improving our setup experience prior to our first commercial launch with connected retail partner Chronodrive.
Over several iterations I refined the setup process by removing 2 steps and clarifying instructions with short looped video demonstrations. One difficulty observed during my user testing was the expectation that pressing the button on hiku should make something happen in the hiku app. This isn’t possible until after hiku is connected to the user’s Wi-Fi network, however. I rewrote the button labels with this in mind. When I used labels that were specific to the step in the process and phrased like what a user would say - for instance “OK, I see lights” rather than “Continue” users were much more likely to tap the buttons and advance through the flow.