Professional Documents
Culture Documents
5-Mobile Presence-Discussions-answers
5-Mobile Presence-Discussions-answers
5-Mobile Presence-Discussions-answers
Mobile Presence
JCU CP3401/5636 1
Case Discussion 1
Building a Mobile Presence
JCU CP3401/5636 2
Mobile First Web Design
JCU CP3401/5636 3
Mobile First Web Design
• Cons
• more difficult for designers who are more comfortable with
the more traditional process (Byers, 2013).
JCU CP3401/5636 4
Responsive Web Design
Pros Cons
• One URL for all • Careful planning
content required, could be a
• A streamlined user costly activity to
experience redesign the
traditional website to
• Flexible orientation responsible mobile
• No redirects version
JCU CP3401/5636 6
Responsive Web Design
• Common mistake:
• Data bloat / Page bloat refers the ever increasing size
of modern web pages.
• You do have to have mobile users download full-size
images meant for big screens and fast speeds.
• Try to reduce HTTP requests and minimize CSS and
JavaScript. Load visible content first and defer
everything else.
JCU CP3401/5636 7
Adaptive Web Design
(Dynamic Serving)
• the server detects the attributes of the
• using predefined templates based on device screen
size along with CSS and JavaScript,
• loads a version of the site that is optimized for the
device.
JCU CP3401/5636 8
Adaptive Web Design
(Dynamic Serving)
Pros Cons
• A custom user • Content forking.
experience
• Easier changes
• Faster loading
• Single URL
JCU CP3401/5636 9
Adaptive Web Design
(Dynamic Serving)
• Common mistakes:
• Faulty device detection, script fail to recognize the
device
JCU CP3401/5636 10
Mobile Web App
(separate to the desktop version)
• Your system detects mobile visitors and redirects them
to your mobile-optimized site (often using a sub-
domain like m.yourname.com).
• Only mobile users will see the separate mobile site.
JCU CP3401/5636 12
Mobile Web App
(separate to the desktop version)
Common mistakes:
• Faulty redirects.
• Missing annotations.
• Inconsistent user experience.
JCU CP3401/5636 13
Mobile Web App
(separate to the desktop version)
JCU CP3401/5636 14
Web App / Native app / Hybrid
App
JCU CP3401/5636 15
Native App
Pros Cons
• Native Low-level and • No one size fits all
high-level APIs solutions, there are
• Can work offline various types of
mobile OS, need to
• Native app develop for different
performance is the platform.
fastest among all
other solutions
• Different approval
process for different
apps stores
JCU CP3401/5636 17
Native App
JCU CP3401/5636 18
Hybrid App
JCU CP3401/5636 19
Hybrid app
Pros Cons
• Cross-platform • Some features may
• Some access to not work offline
native API when
required
• Easy update without
go through
submission approval
for apps store again
JCU CP3401/5636 20
Web App / Native app / Hybrid
App
JCU CP3401/5636 21