This document discusses how wearables will impact mobile app development workflows. It begins by reviewing wearable adoption trends and use cases, such as smartwatches extending smartphones and sensor-based health/fitness apps. It then provides overviews of the Android Wear and Apple Watch development platforms, including their app models and UI elements. The document notes challenges like new hardware constraints but also opportunities like continuous testing on real devices. It concludes by advising developers to leverage capabilities like handoff between devices and consider navigation patterns from the start of wearable app design.
1. How
are
wearables
going
to
disrupt
(Even
More)
the
current
mobile
SDLC
Workflows?
February
2015
2. Ready
to
Plug
in
YOUR
Environment
ü Real
end-‐user
condiIons
ü Enterprise
grade
SLA
ü Open
and
Integrated
plaLorm
ü Global
and
collaboraIve
dev
tesIng
environment
ü Hybrid
Cloud
deployment
model
ü ElasIcity
Perfecto
Mobile
ConInuous
Quality
Lab
Grid
Remote
web
driver
server
ExisIng
Remote
WebDriverclients
REST
API
Device
DOM
Visual
Device
Cloud
Remote
WebDriver
Perfecto
Mobile
extensions
Cloud
Auto
Remote
InteracIve
access
&
Script
Recorders
3. Agenda
• Market
Stats
• Wearable
POV
• Wearable's
Use
Cases
• Android
Wear
and
Apple
WatchKit
Overview
• Wearable’s
Dev.-‐Test
Best
PracKces
• Wearable’s
ImplicaKons
On
SDLC
4. Wearables
AdopIon
Is
Growing
Source:
BI
Intelligence
Smartwatches
will
become
the
wearables
leading
Product
category
(iWatch)
5. Investments
($$)
Are
In
Place
More
than
1.9$
Billion
Invested
in
Wearables
since
2009
Source:
CB
Insights
7. IntroducIon
To
Wearable’s
Connected
compuIng
with/without
displays
Worn
on
body
with
easy
hands-‐free
access
Shows
contextually
relevant
informaIon
to
user
InformaIon
can
be
made
available
at
a
glance
Can
transmit
health
stats
to
server
Can
support,
Augment
and
OpImize
Physical
workforce
8. Wearable’s
POV
Wearable's
will
create
the
internet
of
things
Kpping
point
(Volvo
example)
for
outside
the
home
use
cases
Wearable’s
are
the
newest
version
of
fragmentaIon
Wearable’s
will
introduce
a
new
level
of
complexity
for
Dev.-‐Test
professionals
(Schedule
delays
in
1st
release,
adapt
CI,
AutomaKon,
ConnecKvity,
memory
&
load
tesKng)
In
a
majority
of
the
cases
Mobile
&
Wear’s
are
to
be
considered
as
one
(Dev./
Test
POV)
Accessing
wear’s
as
part
of
SDLC
enforces
the
importance
of
an
Hybrid
Cloud
(mulK
deployment
opKons)
Apple
Watch
and
Apple
Pay
will
be
the
killer
app
(use
case)
of
2015
Wearable’s
technology
will
reduce
smartphones
usage
9. Unique
Use
Cases
For
Wearables
ü Smartphone
extensions
for
usability
purposes
(addressing
events
from
the
smartwatches
like
calls/messages/noKficaKons
OOB)
ü Sensor
based
use
cases
(health
measurements,
fitness
measurements,
Airport
security
etc.)
ü Mobile
Payment
through
iWatch/Wear’s
,
Augmented
visuals,
Stock
inventory
(Modern
Retail)
ü LocaIon
based
acKviKes
(Google
glass)
ü Voice
acKon
based
launch
ü Calendar
&
SmartWatch
Kght
sync
for
easy
Kme
management
(meeKng
alerts
from
smartwatches)
10. IntroducIon
To
Wearables
App
Development
Wearables
apps
may
differ
from
regular
apps
in
• Design
• FuncKonality
(subset
of
apps)
• Usability
• Different
user
interacKon
(micro)
method
• App
size
&
InstallaKon
• HW
constrains
(ba_ery,
CPU)
• New
Sensors
14. Working
With
Apple
Wear’s
(WatchKit)
• Base
app
must
of
course
support
iPhone
–
In
either
methods
– Add
a
WatchApp
target
to
an
exisKng
iOS
App
– Use
glances
(quick
and
lightweight
view
of
your
app
–
swipe
up
on
wear)
– Engage
through
acIonable
noKficaKons
• The
iOS
App
is
responsible
for:
– WatchApp
install
and
management
• WatchKit
and
iOS
RelaKons
Watchkit
extension
15. Apple’s
WatchKit
Framework
-‐
Overview
Unique
UI
Elements
(Line
separator,
Dynamic
date
element)
-‐ WKInterfaceController
-‐ Main
WatchApp
Class
-‐ One
controller
per
screen
of
content
-‐ WKInterfaceGroup
-‐ Used
for
horizontal/VerKcal
layout
and
content
arrangement
-‐ WKInterfaceTable
-‐ Dynamic
content
arrangement
-‐ MulKple
row
types
-‐ WKInterfaceMap
-‐ Non
interacKve
map
snapshot
-‐ WKInterfaceDevice
-‐ Device
specific
informaKon
-‐ Current
Locale
-‐ WKUserNoIficaIonInterfaceController
-‐ StaKc
noKficaKon
-‐ AcKon
bu_ons
18. Apple
WatchKit
Apps
–
Advanced
Tips
Leverage
the
Handoff
API
• TransiKon
between
iOS
and
Watch
• Deep
links
between
wear
app
and
main
iOS
app
Use
cache
for
images
when
not
in
use
(up
to
20MB
of
images)
WatchKit
support
animaIon
with
images
(sequence
image
according
to
duraKon
etc.)
Sefngs
bundle
is
supported
for
wear’s
for
specific
watch
configuraIons
Watch
apps
extends!
iOS
Apps
–
design
them
as
such
Decide
on
your
WatchApp
navigaIon
style
in
the
beginning
• Page
view
vs.
ControllerInterface
implementaKon
19. Basic
Guidelines
-‐
Generic
Do
the
“heavy
lifing”
tasks
on
your
mobile
app
(intensive
processing,
network
communicaKons,
long
Kme
user
acKons,
etc.)
NoKfy
the
Wear
the
results
through
noKficaKon,
sync,
send
data
etc.
between
the
devices
Develop
directly
and
deploy
to
the
wear
pre-‐producKon
• Bundle
the
wear
app
inside
the
mobile
app
prior
to
release
(connected
wear’s
automaKcally
receive
it)
20. Mobile
App
Current
SDLC
ImplicaIons
Mobile
&
Wear’s
Are
One!
• The
case
for
Hybrid
cloud
à
Local,
Private,
Public
become
standard
• New
set
of
unique
devices
(wearables)
to
support,
connecKvity
issues,
governance
(50-‐best-‐wearable-‐tech)
Real
network
condiKon,
wind
tunnel,
system
level
is
a
must,
object
analysis
(Visual,
NaKve)
New
subset
of
mobile
OS
to
support
(Android
Wear,
iOS
Wear)
New
set
of
test
cases
to
develop
and
automate:
• NoKficaKons,
voice,
calendar
based,
sensor
based,
pairing
• App
install
and
upgrade
• DeacKvaKng
wear
apps
and
sync
tests
between
devices
21. DEMO
Pair
a
smartwatch
with
an
Android
Smartphone
and
perform
manual
gestures
and
events
on
the
device
from
the
smartwatch