As I'm going to apply Hungry House services onto the iWatch, I thought it would be beneficial for me to see their current mobile site. To understand if there are any issue that may cause a problem when being transferred onto a smartwatch.
I spend a good 15 minutes looking through the whole app, taking many journeys as if I was a customer. Going through all the settings and filtering sections that the app has to offer. What I found was that Hungry House has a lot of information on their site. They have an extensive range of settings and filters (as seen from the images below). You quickly come across many layers and subcategories of cuisines and settings that the user can look through to find the perfect food, restaurant and even how the food would be delivered. The user has full control over every single step.
Are all these settings and subcategories necessary, and will they benefit the user if applied onto the iWatch? Hungry House can afford to implment a vast filtering system for their desktop and mobile site because the sites and devices are big enough for the user to comfortably filter though the vast amount of information. With an iWatch it would be impossible. The screen resoltuion for the iWatch, especially for the 38mm screen would be impractical, even to implement half of what Hungry House has to offer.
The iWatch version needs to showcase and present only the basics of what Hungry House has to offer. The iWatch version needs to present its self as a light version of the full experience. A version where the user can order their food in the most basic way. It may be be basic but the overall experience and user journey will be efficent and fluid. The app must also translate to its users that the app and the watch work together to creat a unique experience for user in situations where the smartwatch would be a better option over the phone or computer. It could be because the user needs to quickly order food in a few step or a user is drunk on the way home and can't make sense of the mobile or desktop site
No comments:
Post a Comment