This document provides an overview of mobile performance testing. It discusses why mobile performance is important, different types of mobile apps, common performance challenges, tools for testing and profiling apps, and recommendations for optimizing performance. Key points include: mobile users expect fast experiences; slow apps can lose users; challenges include JavaScript execution time, caching, network usage; tools like Mobitest and Android Debug Bridge can monitor performance; recommendations are to minify code, optimize images, and implement efficient caching strategies.

1. Mobile
Performance
Tes1ng
@RupeshDubey
@PriyankDhillon

2. What
to
expect?
• Why
mobile
performance
is
important?
• Different
types
of
mobile
apps.
• Performance
Challenges
• Tools
and
Technique
• Web
apps
Profiling
(Latency,page
audits)
• Na1ve
apps
Profiling
(Memory
leaks)
• Recommenda1ons

3. Why
mobile
perf
is
important?
Source:Blaze

4. Mobile
Users
Expect
equal
speeds
Source:Blaze

5. Users
abandon
slow
apps

6. Mobile
Apps
• Mobile
Browser
apps
– mDOT-­‐
dedicated
mobile
sites
– Responsive
web
design
• Na1ve
Apps
• Hybrid
Apps

7. mDOT
Sites
Source:Velocity

8. Responsive
Web
Apps
Source:BostonGlobe

9. Mobile
Apps
• Mobile
Browser
apps
– Dedicated
mobile
sites
-­‐
mDOT
– Responsive
web
design
• Na1ve
Apps
• Hybrid
Apps

10. Performance
Challenges
• Mobile
Browser
apps
– mDOT-­‐
dedicated
mobile
sites
– Responsive
web
design
• Na1ve
Apps
• Hybrid
Apps

11. Front-­‐End
Vs
Back-­‐End
performance

12. Perf
Challenges
while
browsing
on
mobile
• Radio
Resource
Control
• HTTP
pipelining
• Browser
Cache
• JS
execu1on
1me

13. Radio
Resource
Controlling
and
RTT

14. JS
Execu1on
Time

15. Browser
Cache
Desktop
browser
Cache:
512
MB

16. Browser
Cache
• sqlite3
webviewCache.db
'select
expires
from
cache
order
by
expires
desc;'

17. HTTP
pipelining

18. How
to
Monitor
• MobiTest
/
Web
page
test
• ADB
(
Android
debug
bridge)
• Remote
debugging
for
mobile
safari
• Yslow
• SpriteMe
• Icy
(iOS
specific)

19. Demo

20. Responsive
Web
Design

21. Takeaways
for
Mobile
apps
• Minify
your
java
script
and
CSS
• All
images
have
dimensions
specified
• Have
an
efficient
caching
strategy
• Load
JavaScript
at
the
end
of
the
page
• Lazy
loading
• Different
sizes
of
image
for
Responsive
web
apps
• Don’t
download
extra
CSS
• Serve
low
resolu1on
images
on
smaller
screen

22. Mobile
Apps
• Mobile
Browser
apps
– mDOT-­‐
dedicated
mobile
sites
– Responsive
web
design
• Na9ve
Apps
• Hybrid
Apps

23. Challenges
• Memory
leaks
• CPU
limit
• Network/Bandwidth
• Power
consump1ons

24. Memory
Leaks

25. ARC

26. Power
Consump1on

27. Power
Consump1on(Contd)

28. Network/Bandwidth

29. Takeaways
for
na1ve
apps
• Release
or
free
any
allocated
memory
as
soon
as
you
are
done
using
it.
• Avoid
compu1ng
anything
un1l
you
are
sure
you
actually
need
it.
• Avoid
spinlocks,
polling,
and
other
CPU-­‐hogging
techniques.
• When
prac1cal,
perform
network
requests
in
batches
rather
than
one
at
a
1me.
• Consider
memory-­‐mapping
large
files
instead
of
reading
them
into
RAM.
Doing
so
helps
the
system
manage
memory
more
efficiently.

30. Few
Pointers
for
iOS
App
submission
iOS
Guidelines:
• App
size
should
not
be
more
than
50
MB
for
non-­‐gaming
app.
• Any
memory
leak
and
your
app
is
rejected
• Device
bagery
constraints
• Excessive
hea1ng

31. Ques1ons?