W8 L3 - Mobile UI Strategy Flashcards
1
Q
What is mobile first and what does it mean
A
- “Mobile isn’t just another silo or channel. Instead, it is an all-encompassing catalyst for applications, virtual reality, artificial intelligence and other future innovations…”
- Accessible anywhere
- accessible at any time
2
Q
What are some benefits of being mobile first?
A
- anytime, anywhere
- being ahead of the game
- easier communication
- relationship building
3
Q
what are some considerations with going mobile
A
- Aligns with the company’s business goals/strategies?
- Is supported by a business case?
- Cost
- Market research; who needs it?; will it be used? - Is needed (will satisfy important stakeholder)
- Are there cheaper, more sensible, alternatives?
- Is there an existing mobile strategy?
- Existing mobile users?
- Changes?
- Is just to follow a trend?
4
Q
What are some mobile strategy options
A
- Responsive Web design (RWD)
- The website’s pages are ‘responsive’
Respond to the user’s environment: platform, screen size, and screen orientation
- A single design optimised for multiple devices, adjusting the design based on the device (screen size).
- A fancy website/page.
- Technologies: CSS3 and JavaScript (usually framework)
IT IS MORE FOCUSED ON INFORMATION - Native App
- A native application is a software program that is developed for use on a particular platform or device. Because a native app is built for use on a particular device and its Operating System, it has the ability to use device-specific hardware and software. INTERACTION
- Native applications are the downloadable ‘apps’
- They are platform dependent and run ‘native code’ on the mobile device. - Hybrid App
- Hybrid over Native. Hybrid applications are web applications (or web pages) in the native browser, such as UIWebView in iOS and WebView in Android (not Safari or Chrome). Hybrid apps are developed using HTML, CSS and Javascript, and then wrapped in a native application using platforms like Cordova. INTERACTION
5
Q
How do you assess the business needs
A
Audience
- Who is already coming to existing content via mobile devices?
- Which user group(s) will you target
Content
- What type of content would you need to present?
- Informational v/s interactional
Priority
- Prioritize based on how useful, important or critical specific sections/features of the website are for your users
Budget
- Cost of building and maintaining multiple versions
6
Q
What are the Heuristics of RWD
A
- Content is King!
- Structure the content and optimise for layout
- Design for mobile first
- Focus on core actions
- Consider screen size and device capabilities
- Consider low-data usage
- Flexible everything
- Text, images, buttons, place holders everything is flexible to adapt to the a variety of screen sizes and resolutions (eg. smartphone vs. high definition screen)
- Design for ”progressive enhancement”
- Start with a baseline of core functionality, then increase the richness of UX
7
Q
What are the pros and cons of RWD
A
Pros
Just one website - DOES NOT COST YOU AS MUCH
Cons
Just a website
No offline access
8
Q
What are the pros and cons of Native App
A
PROS
- Leverage ‘phone APIs’
- Multi-touch; graphics; built-in phone components
- Ease of use
- Platform familiarity breeds ease of use.
- Offline access
- Performance
- Not dependent on server
- Documentation
- user guides etc.
CONS
- Store-related
- Platform/Development-related
- Restricted by Ts&Cs of platform and development tools
- Compatibility: device and version
- 1 code base per platform
- Actual app-related
9
Q
What are the pros and cons of Hybrid App
A
Pros
- Allows you to write and maintain a single codebase just like HTML 5 Web apps
- Has access to platform specific capabilities and features just like Native apps
Cons
- This is a niche space and requires extremely knowledgeable and sophisticated programmers and designers to develop and maintain hybrid apps.
- Not ideal for large/growing and high frequency user base
