top of page

Ribot have taught us the art of Simple.

Writer: Nick LansleyNick Lansley

It’s mid-afternoon on a Saturday, and my copy of Tweetdeck is on the screen displaying my favourite filtered Twitter feeds. As you can imagine I have a column filtering “tesco iphone app” and I have to admit I’m enjoying the very many positive comments coming from ‘the real world’.

The team at Ribot are enjoying it too. Given that they designed and built the Tesco Groceries for iPhone app, their enjoyment at watching this very real feedback is even greater than mine (click here and you’ll see what I mean).

Ribot haven’t finished with us yet, though. Their mobile expertise is affecting our thinking and what it means to actually make the customer’s experience better by simplifying it.

It’s a similar story for Tesco Finder – now customers can get directly to the set of products they are looking for and ignore the cacophony of presentation surrounding them. Indeed I’m beginning to identify a new demographic of customer who has avoided big Tesco stores (particularly unfamiliar ones) in the past because they think it would take too long to find what they are looking for, so don’t even attempt to visit.

Teso Finder simplifies the journey to the product by enabling the customer to only look out for the navigation landmarks to get there (such as aisle number signs) and avoid the rest of the information hubbub. This new demographic of customer is now entering our doors – and together customers are using the app to find products at their chosen store at the rate of up to 5 requests a second according to Tesco Finder’s server logs.

Now a confirmation message has come down from the very top of Tesco that we must start work soon to join Tesco Groceries and Tesco Finder together into a single app.

This means that in our work pipeline is your simple guide to Tesco groceries on your smart phone whether in-store, at-home or out-and-about – because, as Ribot have taught us: simpler mean better.

 
 
 

Recent Posts

See All

Comments


Post: Blog2_Post
bottom of page