Mobile exceeds desktop web usage! This was one landmark change which was documented in early 2014. Now, a year later, businesses are still trying to come to the grips with this tectonic plate-shifting change. According to Goldman Sachs, mobile commerce sales would hit $626 billion by 2018, and according to Forrester Research, 54% of the total e-commerce sales would be done on a mobile device in the next three years.
The ubiquitousness of the mobile devices accompanied by the ever improving infrastructure (speed, connectivity, etc) are the catalysts for this growth. But just as every coin has two sides, mobile poses a great challenge for many businesses which they are yet to tame.
One of the most common mistakes firms do, is to presume that users would be navigating through your app, or mobile site in the same manner as they do with a desktop. Simply having an app or a mobile web site should not be your Mobile First Strategy. Providing a good mobile user experience (UX) is indispensable in today’s business environment.
Thank you, for joining us for the webinar on “Mobile UX: Doing it the right way” on Wednesday, February 11, 2015. In this webinar attendees got insights on the various practices, processes and design strategies to create and deliver a rich mobile UX.
THE WEBINAR KEY TAKEAWAYS :
1- Designing an optimal, intuitive and rich UX with improved collaboration and consultative approach
2- Insights on user centric design strategies for mobile
3- Mitigate common challenges in app design and development
4- Enhance your mobile experience with the right balance between standards and creatives
11. • On Web
– Even for the minimum
resolution, plenty of real
estate is available
• On Mobile
– For mobile it is necessary to
start with smaller screen size
Why UCD different on Web and Mobile
12. • On Web
Visual hierarchy & appropriate
placement to guide user’s
attention
• On Mobile
Tappable/target area,
actionable near the thumb,
motor load
UCD difference
Source: uxmovement.com
Web –
As the real estate is available in plenty for web, the architecture is defined based on task priority that they expect it from the user.
Based on task, hierarchy is so arranged that user focuses on the task priority wise. For the visual arrest, certain elements are graphically highlighted as shown in the image.
Mobile –
Whereas the architecture for the mobile is scenario based. Due to unavailability of the real estate, most important tasks are filtered and shown upfront.
As shown in the screenshot, main tasks are displayed upfront and secondary tasks are lined up in the burger menu. This lessens the memory load on the user by displaying the tasks at his/ her initial focus.
Web –
Navigation is task based and in detailed. First level navigation can be shown upfront completely.
Mobile –
Whereas for mobile, navigation gets prioritized. As shown in the image, all the options are categorized and are placed under single menu.
Web –
Demographics is secondary factor for web, which can impact the scenarios but not up to a great extent.
Mobile –
Demographics is considered as an important factor for mobile which can influence the scenarios.(Context/ surroundings/ hardware/ software capabilities)
Web –
Task flow is can be more detailed, with user having options to complete the task with some customized options.
Mobile –
Task flow is precise and is intended to get completed in fewer steps.
Gestures –
People are becoming familiar with touch gestures like -swiping, dragging, pinching, etc. These gestures should be considered for interactions.
Orientation Change –
Wireframes for orientation change i.e. portrait to landscape and vice-versa should be considered for content resizing, switching and display.
Layout for all types –
Button sizes and clickable area should be considered for all types of fingers and layouts.
Devices Compatibility –
Compatibility for interactions, content, tasks should be considered for various devices and platforms.