GetHelp! Case review

The interface is attractive as it can be seen that effort was put into designing icons and images to represent functions on the site. The application is very feature rich and the team made the decision to include several key features on the landing page for easy access.

The application can employ current UI trends to make the application more user friendly

1)      Single focus task

Many websites such as Google now have a clean and simple landing page where user’s attention is directed to a single focus task. GetHelp! can employ similar design element to reduce the clutter and features displayed on the page to encourage user action.

2)      Visual and pictures

Another trend startups employ is to place more emphasis on content through the use of visuals and pictures. Pinterest is a good example which uses many visuals in their products. GetHelp! can have a feature which generates a group of images for users to choose based on the keywords extracted from the task.

3)      Collapsed Content

GetHelp! highlighted 5 features that they placed on the front page. Instead of having all features accessible on 1 page, they can collapsed content and hide them into different tabs. This will allow user quick access to the menu without overcrowding the interface.

4)      Pop up box

To encourage user interaction with the site, the request for help form can be in a pop up box instead of directing users to another page. This way, users can easily return to whatever he/she is doing with minimal interruption.

                                                               

To convert the application into a mobile application, we must first determine the user behaviour of GetHelp! on mobile. In my opinion, the focus of the mobile application should allow users to post requests and receive help on the go.

Thus the first thing the team should do is to develop a high level feature list and a flow chart illustrating the different pages. This designing process will help the team by clearly drawing out the process in which users will interact with the application.

For GetHelp! the main features the application should have is the ability to submit a request, view all requests submitted and answered by user and view requests by others.

Once the flow chart has been constructed, the designers and developers can start writing the codes. Along the way, the development team should constantly test each features of the application as it rolls out to ensure that no errors or bugs are carried forward to the next features. Before launching it, team should invite external users to test ensure the application is working as promised.