by Eugenio Santiago The Apple Watch, released this past Spring, has caused companies to pay close attention to the quickly evolving wearable space. Consumers are looking to see if there is a tipping point for […]
by Kathleen Henning and Phil McGuinness In part two of our series on mobile payments, Phil and Kathleen review a few exciting mobile payment options and talk about the near future of mobile payment technology. […]
By: Kathleen Henning and Phil McGuinness After a challenging experience with mobile payments at a New York music festival, our researchers decided to get together and assess two of the leading mobile payment options currently on […]
A hot topic right now in mobile user experience is the debate between providing an HTML5 web app versus a more traditional Native OS app. Simply put, HTML5 is a method of programming a mobile website to behave like an app (think m.youtube.com) which can be accessed through any modern tablet or smartphone browser. Conversely, apps written for a Native OS are developed to run directly on Android or iOS smartphones (they are designed for each native platform), and must be downloaded through the GooglePlay Store or Apple App Store. Both approaches are a great way to provide web content to smartphone and tablet users, and they each have their own strengths and weaknesses. Which of these approaches is right for your business? At Key Lime Interactive, we are exploring this question in depth, and have key information to help you make the right decision
Take figure 1: The Chase Mobile app.
A few issues jump out that appear to be quick-fix usability problems. First, the bottom menu bar seen here is being phased out because newer phones don’t possess the touch buttons that run on Android 4.1 (Jellybean). You might note that it also takes up a considerable amount of screen space making it undesirable. On the right hand side you can see the right pointing carets (sic) which are an iOS feature, not an Android OS feature. Additionally, at the top there is no indication of which app you’re presently using, or how to navigate backward to previous screens. We’re thinking that there should be an action bar of some kind to help with navigation within the app. Finally, after looking more closely at figure 1 you may have also noted that there is no Chase Bank insignia or identification. Despite the familiar design for iOS users, the app seems to have a number of usability issues that are easy to identify. While an iOS user may find this App is easy to use, Android OS users have reportedly found the interface to be confusing and we predict that such a user is at risk to abandon.