Yelp iPhone client redesign: Problems and thought process

Yelp iPhone client redesign: Problems and thought process

Yelp is a review website that has been published for more than ten years. It originated in the United States and has developed globally. Yelp has information on various stores, such as restaurants, coffee shops, gas stations, shopping malls, etc. People can find a variety of stores on it and write reviews for them, check in, or upload photos and videos. In addition, Yelp is also a social platform for life, where people can see the stores that their friends have recently visited and the reviews they have written.

Yelp iPhone app

Yelp in the iTunes App Store

Yelp is a large website with a large amount of store information and user-generated content. When the iPhone client carries this information, it must handle the information architecture well, because this greatly affects the user experience. Currently, the functional framework of the Yelp iPhone client is relatively complex, mainly divided into five basic pages: Nearby, Search, Publish, About Me, and More.

  • Nearby Stores: Displays nearby stores and recommended categories. Users can quickly find stores here.

  • Search: Users can search based on keywords or add filters for more precise searches.

  • Release: divided into three categories: comments, check-ins, and uploading photos and videos.

  • About Me: Display personal information.

  • More: Integrate auxiliary functions such as bookmarks, information flow, and lists of stores you have visited.

The current functional framework of the Yelp iPhone client (click to see a larger image)

Problems

1. Function entrances are scattered

When a user wants to find a store:

  • If it is a store you have visited/bookmarked before, you can search directly on the More page, where you can find a list of stores you have visited and a list of bookmarks.

  • If it is a new store (or you have visited it but it is too long ago to retrieve it or you have not bookmarked it), and you know the name/keywords, you can enter text to search on the Nearby page and Search page;

  • If you don't know any information (or forgot the name/keyword), you can search for nearby shops based on geographical location, otherwise you will need to search through the shop category directory.

When a user wants to post content:

  • You can directly click on the super tab and select a category. The page will jump to the search page first, load nearby shops or allow users to enter text, select a shop and then fill in the content.

  • Or follow the above process to enter the store details page, then select the category and fill in the content.

Yelp’s interactive process of finding stores and publishing content

There are many ways to find a store or post content. This is not without its benefits, but it can easily confuse users. For example, if I want to write a review for a restaurant, there are two scenarios:

  • If you haven't left the restaurant yet, you can directly select a category to post in the super tab, and the app will automatically load nearby stores, with the restaurant you are in at the top of the list.

  • However, if the user has already left the restaurant and then remembers to leave a review, it would be faster to enter the store details page from the historical browsing list. On the contrary, if the user posts from the super tab, they still have to manually enter text to search.

Don’t just rely on business functions to divide modules, otherwise the experience design will be a mess.

2. Duplicate function entry

Except for the publishing page, the rest of the pages carry a lot of information and there is duplication. Zooming in on the functional framework will make it clear at a glance. Super tab is where users can quickly publish content, and the same entrance can be found in the About Me page; bookmarks, events and other pages not only appear in the About Me page, but can also be found in the More page. If users are used to using one entrance, the other one will be redundant, making the page unnecessarily complicated.

Functional framework part 1

The Nearby page is very similar to the Search page. Selecting a category on the former will redirect you to the search results page (shop list) on the latter, which saves you the trouble of entering text. The search box at the top of the former page is exactly the same as the search box on the latter. There are duplicate shop categories in the main directory of the former and popular categories in the secondary directory. I believe I am not the only one who is confused by this.

Functional framework part 2

Clear and unambiguous logic is the key to whether a product with complex information architecture provides a good user experience.

3. The information flow (Feed) is too weakened

In addition to having a large amount of store information and high-quality user-generated content, Yelp also has strong social attributes, allowing people to see the dynamics of their friends and nearby users. People do not just use it as a search tool or open it when they go out, but can use Yelp to make friends and interact with others. This helps to increase user participation and the desire to create content.

On the web, Yelp does this - log in to the website, and your friends' latest updates will be displayed on the homepage. On the iPhone client, however, user-generated content is relatively scattered. Except for the part associated with stores, the rest is scattered on the user page and the More page, lacking an independent information flow page.

Left: Yelp Web homepage, middle: Yelp iPhone client user page, right: Yelp iPhone client More page

#p#

Redesign your thinking process

Yelp's information architecture is complex and contains a lot of content. I started with the most basic data and replanned Yelp's page layout. Yelp's data is mainly divided into three categories: stores, user-generated content, and users. Store data includes information such as name, address, and category. User-generated content data is divided into three categories: reviews, photos/videos, and check-ins. Each user-generated content data is associated with a store and a user.

Yelp Basic Information Framework

Users only care about information related to them, such as friends, people nearby, and shops they are interested in. These are effective user-generated content. Therefore, user-generated content needs to be displayed to users according to certain relevance. The most intuitive way is to create an independent information flow page and integrate the content of friends and nearby users here. Integrate the user's own content into the personal page, and classify the user-generated content related to the store together on the store page. As shown in the figure below.

Create an independent information flow page

Stores have independent detail pages, which still need to be organized before they can be displayed to users. In addition to the category directory (which Yelp does now), geographic location, browsing history, and bookmarks are also relevant to users - they allow users to quickly find nearby, previously browsed, or marked stores. Browsing history and bookmarks are active operations by users, and they should be classified into personal pages.

Further organize the shop

But if you want to discover new shops, browsing history and bookmarks are useless. At this time, you must use geographic location or directory to classify. Therefore, when users need to initiate a search, they need to be allowed to discover these unknown shops through geographic location and directory (or recommend popular shops through operations). At this point, the functional modules are basically clear, as shown in the figure below.

User behavior and improved basic functional modules

*** is the core publishing function. Currently, the way to publish content using super tab is to search first and then fill in the form, which ignores the consideration of the scene. In addition to loading nearby shops or searching by inputting text, integrating shops in bookmarks and historical browsing records is also helpful to simplify the content publishing process and make users more accustomed to using super tab.

Content publishing portal

Redesign

The functional interface is adjusted to Nearby, Search, Publish, Feed , and About Me. The original catalog categories in the Nearby page are integrated into the search page, and a Feed page is added to display friends, nearby people, and popular reviews. The original More page is cancelled, and the functions are integrated into the About Me page and settings.

Yelp iPhone app redesign

The Search page displays the search results of shops. You can add filter conditions to refine the search and search by shop category. Click the search box to display recommended categories and popular categories. The secondary page is all categories.

Search page and store category directory page

After clicking the super tab and selecting the publishing category, nearby shops and recently browsed shops are displayed, and bookmarks and entrances to all nearby shops are provided.

The interface for selecting a store when publishing content

The About Me page provides access to bookmarks, events, friend lists, published reviews, and posted photos. It displays recently visited stores and My Feed. Detailed settings and messages are located on the left and right sides of the menu bar.

<<:  Getting Started with WatchKit: Creating a Simple Guessing Game

>>:  Experience sharing: How do we promote APP?

Recommend

Apple App Store’s latest review rules for 2016!

serial number Chinese content 1.1 When developing...

How much does it cost to make a lighting applet in Dafeng?

What is the price of producing Dafeng Lighting Mi...

Flash floods occur! Remember these to save yourself!

Since June this year, some parts of my country ha...

A brief discussion on automobile brand marketing!

This article talks about my views on automobile m...

Remember! Do not perform time-consuming operations in the UI main thread

question Since the release of Android Ice Cream S...

Apple iCloud briefly down, possibly to fix new iOS 8 vulnerability

Apple has confirmed that iCloud has temporarily b...

As a developer, how do you think Apple should improve its developer tools?

[[164459]] My colleague Alex Denisov and I have d...