Don't use it or you'll lose it

Рассмотрим, как можно использовать возможности вашего устройства (в том числе, его сенсоров) и некоторые приемы UX для того, чтобы улучшить производительность и удобство использования вашего приложения.

Transcript

1. Don’t use it or you’ll lose it by Royi Benyossef Battery and network performance
2. Introduction Royi Benyossef
3. Android developer since 2009 Introduction Royi Benyossef
4. Android developer since 2009 Tech community activist, speaker and founder Introduction Royi Benyossef
5. Android developer since 2009 Tech community activist, speaker and founder Mentor at * accelerator Introduction Royi Benyossef
6. Android developer since 2009 Tech community activist, speaker and founder Mentor at * accelerator Google expert since 2013 Introduction Royi Benyossef
7. Android developer since 2009 Tech community activist, speaker and founder Mentor at * accelerator Google expert since 2013 Ecosystem relations manager at Samsung NEXT Tel-Aviv Introduction Royi Benyossef
8. Introduction Samsung NEXT Software and services startups and products
9. Introduction Samsung Next Tel-aviv Software and services startups and products: - Early stage investments (seed round to round B)
10. Introduction Samsung Next Tel-aviv Software and services startups and products: - Early stage investments (seed round to round B) - Product creation
11. Introduction Samsung Next Tel-aviv Software and services startups and products: - Early stage investments (seed round to round B) - Product creation - M&A
12. Introduction Samsung Next Tel-aviv Software and services startups and products: - Early stage investments (seed round to round B) - Product creation - M&A Contact: royi.benyossef@samsungnext.com
13. Identifying and explaining the problem Prologue
14. Prologue What seems to be the problem?
15. Prologue We use apps everywhere What seems to be the problem?
16. Prologue We use apps everywhere Our desires change based on the environment What seems to be the problem?
17. Prologue We use apps everywhere Our desires change based on the environment Apps must adapt What seems to be the problem?
18. Prologue Problem example Apps need data
19. Prologue Problem example Apps need data Wi-Fi data is free
20. Prologue Problem example Apps need data Wi-Fi data is free 3G/4G data costs money
21. Prologue Problem example Apps need data Wi-Fi data is free 3G/4G data costs money All of them drain the battery
22. Prologue Problem example Apps need data Wi-Fi data is free 3G/4G data costs money All of them drain the battery Users don’t like losing money or battery!
23. Prologue Problem example Apps need data Wi-Fi data is free 3G/4G data costs money All of them drain the battery Users don’t like losing money or battery! However...
24. Prologue Problem example Apps need data Wi-Fi data is free 3G/4G data costs money All of them drain the battery Users don’t like losing money or battery! Users want the best UX! the second she wakes up... Does not like waiting! Wants fresh data...
25. Prologue Problem example
26. Prologue Problem example Apps need data Wi-Fi data is free 3G/4G data costs money All of them drain the battery Users don’t like losing money or battery! Users want the best UX! Internet is not everywhere!!!
27. Prologue Problem example Apps need data Wi-Fi data is free 3G/4G data costs money All of them drain the battery Users don’t like losing money or battery! Users want the best UX! Internet is not everywhere!!! (= Example: metro!)
28. Prologue Problem example Don’t panic! ? ? ? ? ?? ? ?
29. Prologue Problem example Don’t panic! We’re here to help
30. Battery Insert funny(-ish) subheader here
31. Battery Glossary Radio
32. Battery Glossary Radio: • That thing that connects you to cell towers
33. Battery Glossary Radio: That thing that connects you to cell towers • Phone calls + SMS + internet
34. Battery Glossary Radio (= internet) Radio baseline mode
35. Battery Glossary Radio (= internet) Radio baseline mode: • Radio’s almost off
36. Battery Glossary Radio (= internet) Radio baseline mode: Radio’s almost off • Uses almost no power
37. Battery Glossary Radio (= internet) Radio baseline mode: Radio’s almost off • Uses almost no power (100 mA)
38. Battery Glossary Radio (= internet) Radio baseline mode (does nothing, uses nothing) Radio download mode
39. Battery Glossary Radio (= internet) Radio baseline mode (does nothing, uses nothing) Radio download mode: • Radio working at full power
40. Battery Glossary Radio (= internet) Radio baseline mode (does nothing, uses nothing) Radio download mode: Radio working at full power • POWER!!! (400 mA)
41. Battery Glossary Radio (= internet) Radio baseline mode (does nothing, uses nothing) Radio download mode (working, needs POWER!!!) Radio idle mode
42. Battery Glossary Radio (= internet) Radio baseline mode (does nothing, uses nothing) Radio download mode (working, needs POWER!!!) Radio idle mode: Does (almost) nothing • Still uses power
43. Battery Glossary Radio (= internet) Radio baseline mode (does nothing, uses nothing) Radio download mode (working, needs POWER!!!) Radio idle mode: Does (almost) nothing • Still uses power (300 mA)
44. Battery Glossary Radio (= internet) Radio baseline mode (does nothing, uses nothing) Radio download mode (working, needs POWER!!!) Radio idle mode: Does (almost) nothing Still uses power (300 mA) • Lasts up to 90 seconds
45. Battery Glossary Radio (= internet) Radio baseline mode (does nothing, uses nothing) Radio download mode (working, needs POWER!!!) Radio idle mode: Does (almost) nothing Still uses power (300 mA) • Lasts up to 90 seconds (!!!)
46. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow
47. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow: • Phone radio is at “baseline”
48. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow: Phone radio is at “baseline” • App A needs to fetch from server
49. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow: Phone radio is at “baseline” App A needs to fetch from server • Radio goes to “download”
50. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow: Phone radio is at “baseline” App A needs to fetch from server Radio goes to “download” • Data downloaded
51. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow: Phone radio is at “baseline” App A needs to fetch from server Radio goes to “download” Data downloaded • Radio goes to “idle”
52. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow: Phone radio is at “baseline” App A needs to fetch from server Radio goes to “download” Data downloaded Radio goes to “idle” • Radio waits 90 seconds (in “idle”)
53. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow: Phone radio is at “baseline” App A needs to fetch from server Radio goes to “download” Data downloaded Radio goes to “idle” Radio waits 90 seconds (in “idle”) • Radio goes to “baseline”
54. Battery Glossary Radio (= internet, modes = baseline, download, idle) Workflow: Phone radio is at “baseline” App A needs to fetch from server Radio goes to “download” Data downloaded Radio goes to “idle” Radio waits 90 seconds (in “idle”) Radio goes to “baseline”
55. Battery Real workflow 08:00 - Royi puts phone in pocket
56. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes)
57. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00)
58. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00) 09:07 - App C update (FCM induced)
59. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A update (every 60 minutes)
60. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A update (every 60 minutes) 09:35 - App G update (every 2 hours)
61. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A update (every 60 minutes) 09:35 - App G update (every 2 hours) ...
62. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A update (every 60 minutes) 09:35 - App G update (every 2 hours) ... 13:30 - Royi checks the phone in his pocket
63. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A update (every 60 minutes) 09:35 - App G update (every 2 hours) ... 13:30 - Royi checks the phone in his pocket (= 55% battery)
64. Battery Real workflow 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A update (every 60 minutes) 09:35 - App G update (every 2 hours) ... 13:30 - Royi checks the phone in his pocket (= 55% battery?!)
65. Battery Possible solutions
66. Battery Possible solutions Use the radio less
67. Battery Possible solutions Use the radio less
68. Battery Possible solutions Use the radio less Use the radio more efficiently
69. Battery Possible solutions Use the radio more efficiently How?
70. Battery Let sleeping radios lie Use call batching enabled API
71. Battery Let sleeping radios lie Use call batching enabled API - Letting Android batch calls according to time and urgency
72. Battery Let sleeping radios lie Use call batching enabled API Letting Android batch calls according to time and urgency - Less calls = same data with less idle time = PROFIT!
73. Battery Let sleeping radios lie Before batching 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A update (every 60 minutes) 09:35 - App G update (every 2 hours) ... 13:30 - Royi checks the phone in his pocket
74. Battery Let sleeping radios lie After batching 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App A,B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A,C update (every 60 minutes) 09:35 - App G update (every 2 hours) ... 13:30 - Royi checks the phone in his pocket
75. Battery Let sleeping radios lie Use call batching enabled API: • FCM network manager
76. Battery Let sleeping radios lie Use call batching enabled API: • FCM network manager (requires Google Play Services)
77. Battery Let sleeping radios lie Use call batching enabled API: FCM network manager (requires Google Play Services) • JobScheduler
78. Battery Let sleeping radios lie Use call batching enabled API: FCM network manager (requires Google Play Services) • JobScheduler (requires Android 5.0+)
79. Battery Let sleeping radios lie Use call batching enabled API: FCM network manager (requires Google Play Services) JobScheduler (requires Android 5.0+) • SyncAdapter
80. Battery Let sleeping radios lie Use call batching enabled API: FCM network manager (requires Google Play Services) JobScheduler (requires Android 5.0+) • SyncAdapter (complex implementation)
81. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications
82. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications - Push receivers work while radio is at baseline mode
83. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Push receivers work while radio is at baseline mode - The server notifies you when something changed
84. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Push receivers work while radio is at baseline mode The server notifies you when something changed - Nothing’s changed, cancel call = no wasted idle and downloading times
85. Battery Let sleeping radios lie Before push 08:00 - Royi puts phone in pocket 08:15 - App A update (every 60 minutes) 09:00 - App A,B update (every day at 09:00) 09:07 - App C update (FCM induced) 09:15 - App A,C update (every 60 minutes) 09:35 - App G update (every 2 hours) ... 13:30 - Royi checks the phone in his pocket
86. Battery Let sleeping radios lie After push 08:00 - Royi puts phone in pocket 08:55 - App A push (FCM induced) 09:00 - App A,B update (every day at 09:00) 09:07 - App C push (FCM induced) 09:15 - App A,C update (batched) 09:35 - App G update (every 2 hours) ... 13:30 - Royi checks the phone in his pocket
87. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications
88. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Use system connectivity check API
89. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Use system connectivity check API - Searching for connectivity is more costly than calls
90. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Use system connectivity check API Searching for connectivity is more costly than calls - App level queries keeps app loaded and the CPU running
91. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Use system connectivity check API Searching for connectivity is more costly than calls App level queries keeps app loaded and the CPU running - Apps rarely use exponential back-off algorithms
92. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Use system connectivity check API: • ConnectivityManager
93. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Use system connectivity check API: • ConnectivityManager (one batched check for all apps, not keeping app loaded)
94. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Use system connectivity check API: ConnectivityManager (one batched check for all apps) • Schedulers
95. Battery Let sleeping radios lie Use call batching enabled API Use FCM push notifications Use system connectivity check API: ConnectivityManager (one batched check for all apps) • Schedulers (use ConMag automatically, use exponential back-off)
96. Battery appendix Little thing to pay attention to
97. Battery appendix Doze
98. Battery appendix Doze Was Introduced as part of Lollipop
99. Battery appendix Doze Was Introduced as part of Lollipop Applies when:
100. Battery appendix Doze Was Introduced as part of Lollipop Applies when: • Screen is off
101. Battery appendix Doze Was Introduced as part of Lollipop Applies when: Screen is off • Stationary
102. Battery appendix Doze Was Introduced as part of Lollipop Applies when: Screen is off • Stationary (not moving = on a desk/stand)
103. Battery appendix Doze Was Introduced as part of Lollipop Applies when: Screen is off Stationary (not moving = on a desk/stand) • Not charging
104. Battery appendix Doze Was Introduced as part of Lollipop Doze applies when device is unused & not charging Doze was improved as part of Marshmallow
105. Battery appendix Doze Was Introduced as part of Lollipop Doze applies when device is unused & not charging Doze was improved as part of Marshmallow to detect: • Activity = walking
106. Battery appendix Doze Was Introduced as part of Lollipop Doze applies when device is unused & not charging Doze was improved as part of Marshmallow to detect: Activity = walking • Screen off
107. Battery appendix Doze Was Introduced as part of Lollipop Doze applies when device is unused & not charging Doze was improved as part of Marshmallow to detect: Activity = walking Screen off • Not charging
108. Battery appendix Doze Was Introduced as part of Lollipop Doze applies when device is unused & not charging Doze was improved as part of Marshmallow to detect: • Device is in-pocket/in-bag
109. Battery appendix Doze Was Introduced as part of Lollipop Applies when device is unused & not charging When applied
110. Battery appendix Doze Was Introduced as part of Lollipop Applies when device is unused & not charging When applied: • It blocks all network operations
111. Battery appendix Doze Was Introduced as part of Lollipop Applies when device is unused & not charging When applied: • It blocks all network operations (except for “maintenance windows”)
112. Battery appendix Doze Was Introduced as part of Lollipop Applies when device is unused & not charging When applied it forces network batching
113. Battery appendix Doze Was Introduced as part of Lollipop Applies when device is unused & not charging When applied it forces network batching To comply
114. Battery appendix Doze Was Introduced as part of Lollipop Applies when device is unused & not charging When applied it forces network batching To comply: • Test app while in doze mode
115. Battery appendix Doze Was Introduced as part of Lollipop Applies when device is unused & not charging When applied it forces network batching To comply: Test app while in doze mode • If applicable - set right priority for AlarmManager
116. Battery appendix Doze Was Introduced as part of Lollipop Applies when device is unused & not charging When applied it forces network batching To comply: Test app while in doze mode • If applicable - set right priority for AlarmManager (=setAndAllowWhileIdle()/setExactAndAllowWhileIdle())
117. Battery appendix Before Doze 23:00 - Royi goes to sleep 00:00 - App B update 01:13 - App E update 02:00 - App C, D update 03:15 - App A update 04:00 - App B, D update 05:30 - Royi checks phone on night stand
118. Battery appendix Before Doze 23:00 - Royi goes to sleep 00:00 - App B update 01:13 - App E update 02:00 - App C, D update 03:15 - App A update 04:00 - App B, D update 05:30 - Royi checks phone on night stand 05:31 - Royi is angry because he has 23% battery
119. Battery appendix After Doze 23:00 - Royi goes to sleep 00:00 - App B update 01:30 - App B,E update 02:00 - App C, D update 03:15 - App A update 04:00 - App A, B, C, D update 05:30 - Royi checks phone on nightstand
120. Battery appendix After Doze 23:00 - Royi goes to sleep 00:00 - App B update 01:30 - App B,E update 02:00 - App C, D update 03:15 - App A update 04:00 - App A, B, C, D update 05:30 - Royi checks phone on nightstand 05:31 - Royi is happy because he has 43% battery
121. Network usage Day to day data diet
122. Network usage Motivation reminder
123. Network usage Motivation reminder Battery saved by using the radio more efficiently
124. Network usage Motivation reminder Battery saved by using the radio more efficiently: (= Less calls)
125. Network usage Motivation reminder Battery saved by using the radio more efficiently: (= Less calls = less “radio idle mode time”)
126. Network usage Motivation reminder Battery saved by reducing “radio idle mode time” - Done!
127. Network usage Motivation reminder Battery saved by reducing “radio idle mode time” - Done! To do
128. Network usage Motivation reminder Battery saved by reducing “radio idle mode time” - Done! To do: • Reducing radio download mode time
129. Network usage Motivation reminder Battery saved by reducing “radio idle mode time” - Done! To do: Reducing radio download mode time • Improving UX while reducing radio download time
130. Network usage The problem with polling Calling the backend even if nothing changed
131. Network usage The problem with polling Calling the backend even if nothing changed (+ Idle mode)
132. Network usage The problem with polling Calling the backend even if nothing changed Re-downloading data again and again
133. Network usage The problem with polling Calling the backend even if nothing changed Re-downloading data again and again (+ redundant download mode time)
134. Network usage The problem with polling Calling the backend even if nothing changed Re-downloading data again and again (+ redundant download mode time) (+ wasting data plan)
135. Network usage The problem with polling Calling the backend even if nothing changed Re-downloading data again and again (+ redundant download mode time) (+ wasting data plan)
136. Network usage Fetching fetchingly Optimize fetching methods
137. Network usage Fetching fetchingly Optimize fetching methods: • Freshness headers
138. Network usage Fetching fetchingly Optimize fetching methods: • Freshness headers - Far smaller download time footprint
139. Network usage Fetching fetchingly Optimize fetching methods: • Freshness headers Smaller download time footprint - Easy impl. on both client and server
140. Network usage Fetching fetchingly Optimize fetching methods: • Freshness headers Smaller download time footprint Easy impl. - Con: still polling (+ Idle mode time)
141. Network usage Fetching fetchingly Optimize fetching methods: Easy (freshness headers) • Firebase Cloud Messaging push
142. Network usage Fetching fetchingly Optimize fetching methods: Easy (freshness headers) • FCM push: - Good performance
143. Network usage Fetching fetchingly Optimize fetching methods: Easy (freshness headers) • FCM push: - Good performance (= No Idle, No download)
144. Network usage Fetching fetchingly Optimize fetching methods: Easy (freshness headers) • FCM push: Good performance - Harder impl.
145. Network usage Fetching fetchingly Optimize fetching methods: Easy (freshness headers) Medium (push update notification) • Advanced
146. Network usage Fetching fetchingly Optimize fetching methods: Easy (freshness headers) Medium (push update notification) • Advanced (real time databases)
147. Network usage Fetching fetchingly Optimize fetching methods Optimize payloads
148. Network usage Fetching fetchingly Optimize fetching methods Optimize payloads: • Diff only
149. Network usage Fetching fetchingly Optimize fetching methods Optimize payloads: Diff only • Gzip compression
150. Network usage Fetching fetchingly Optimize fetching methods Optimize payloads: Diff only Gzip compression • Advanced formats
151. Network usage Fetching fetchingly Optimize fetching methods Optimize payloads: Diff only Gzip compression • Advanced formats (FlatBuffers)
152. Network usage Fetching fetchingly Optimize fetching methods Optimize payloads: Diff only Gzip compression Advanced formats (FlatBuffers) • Segmentation
153. Network usage Fetching fetchingly Optimize fetching methods Optimize payloads: Diff only Gzip compression Advanced formats (FlatBuffers) • Segmentation (paging & indexing)
154. Anticipate your users Understand when it’s OK to binge and when it’s best to be frugal
155. Anticipate your users Available data points to consider Misc. device listeners
156. Anticipate your users Available data points to consider Misc. device listeners: • Screen state
157. Anticipate your users Available data points to consider Misc. device listeners: • Screen state (on/off)
158. Anticipate your users Available data points to consider Misc. device listeners: Screen state (on/off) • Network state
159. Anticipate your users Available data points to consider Misc. device listeners: Screen state (on/off) • Network state (3G, WiFi, nothing)
160. Anticipate your users Available data points to consider Misc. device listeners: Screen state (on/off) Network state (3G, WiFi, nothing) • Battery state
161. Anticipate your users Available data points to consider Misc. device listeners: Screen state (on/off) Network state (3G, WiFi, nothing) • Battery state (OK, low, charging)
162. Anticipate your users Available data points to consider Misc. device listeners: Screen state (on/off) Network state (3G, WiFi, nothing) Battery state (OK, low, charging) • Dock state
163. Anticipate your users Available data points to consider Misc. device listeners: Screen state (on/off) Network state (3G, WiFi, nothing) Battery state (OK, low, charging) • Dock state (none, car, desk)
164. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API
165. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: • Activity
166. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: • Activity (walking, running, cycling, driving, stationary)
167. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: Activity (walking, running, cycling, driving, stationary) • Location
168. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: Activity (walking, running, cycling, driving, stationary) • Location (Lat/Long, Google Places)
169. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: Activity (walking, running, cycling, driving, stationary) Location (Lat/Long, Google Places) • Physical web
170. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: Activity (walking, running, cycling, driving, stationary) Location (Lat/Long, Google Places) • Physical web (Beacons nearby)
171. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: Activity (walking, running, cycling, driving, stationary) Location (Lat/Long, Google Places) Physical web (Beacons nearby) • Headphones
172. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: Activity (walking, running, cycling, driving, stationary) Location (Lat/Long, Google Places) Physical web (Beacons nearby) • Headphones (yes/no)
173. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API: Activity (walking, running, cycling, driving, stationary) Location (Lat/Long, Google Places) Physical web (Beacons nearby) • Headphones (yes/no) - take that iPhone users!
174. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) - Supported back to Froyo (2.2)
175. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) - *Supported back to Froyo (2.2)
176. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) - *Supported back to Froyo (2.2) *Caution: getBeaconState() is only supported on devices running API level 18 (Jelly Bean) or higher. If calling from a device running an earlier version, getStatus() will return status code API_NOT_AVAILABLE.
177. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) *Supported back to Froyo (2.2) - Permissions: - Beacons & location = FINE_LOCATION
178. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) *Supported back to Froyo (2.2) - Permissions: Beacons & location = FINE_LOCATION - Activity = ACTIVITY_RECOGNITION
179. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) *Supported back to Froyo (2.2) - Permissions: Beacons & location = FINE_LOCATION Activity = ACTIVITY_RECOGNITION - Headphones & time = NONE
180. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) *Supported back to Froyo (2.2) Permissions needed - Outputs
181. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) *Supported back to Froyo (2.2) Permissions needed - Outputs: - Snapshot
182. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) *Supported back to Froyo (2.2) Permissions needed - Outputs: - Snapshot = current user’s context
183. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) *Supported back to Froyo (2.2) Permissions needed - Outputs: Snapshot = current user’s context - Fence = register a listener (flag or combo)
184. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) Misc.
185. Anticipate your users Available data points to consider Misc. device listeners (screen, network, battery, dock) Awareness API (Activity, location, Beacons, Headphones) Misc. (time, calendar and schedule)
186. Anticipate your users Available data points to consider • Connectivity • Battery • Activity • Location • Time of day • Calendar • Weather • Ear phones yes/no
187. Anticipate your users Connectivity On Wi-Fi
188. Anticipate your users Connectivity On Wi-Fi: • Feel free to fetch more often
189. Anticipate your users Connectivity On Wi-Fi: Feel free to fetch more often • Fetch data for later
190. Anticipate your users Connectivity On Wi-Fi: Feel free to fetch more often • Fetch data for later (*if you can cache it)
191. Anticipate your users Connectivity On Wi-Fi: Feel free to fetch more often • Fetch data for later (you MUST cache it)
192. Anticipate your users Connectivity On Wi-Fi (feel free-er) On metered networks
193. Anticipate your users Connectivity On Wi-Fi (feel free-er) On metered networks (depends)
194. Anticipate your users Battery Charged/charging
195. Anticipate your users Battery Charged/charging (go nuts)
196. Anticipate your users Battery Charged/charging (go nuts) <50%
197. Anticipate your users Battery Charged/charging (go nuts) <50% (be more careful)
198. Anticipate your users Battery Charged/charging (go nuts) <50% (be more careful) <20%
199. Anticipate your users Battery Charged/charging (go nuts) <50% (be more careful) <20% (mission critical only!)
200. Anticipate your users Activity Walking/running/driving?
201. Anticipate your users Activity Walking/running/driving? • Sport results app: fetch less
202. Anticipate your users Activity Walking/running/driving? • Sport results app: fetch less • Navigation/music app: user notification
203. Anticipate your users Activity On the go (depends)
204. Anticipate your users Activity On the go (depends) On the couch?
205. Anticipate your users Activity On the go (depends) On the couch? • Stationary • Location = home/office • Connectivity = Wi-Fi • No upcoming meetings?
206. Anticipate your users Activity On the go (depends) On the couch? • Stationary • Location = home/office • Connectivity = Wi-Fi • No upcoming meetings? = Go absolutely wild!
207. Anticipate your user Battery is low Consider the following
208. Anticipate your user Battery is low: - Good ideas: - Give the user a choice Consider the following
209. Anticipate your user Battery is low: - Good ideas: Give the user a choice - Decrease activity Consider the following
210. Anticipate your user Battery is low: - Good ideas: Give the user a choice - Decrease activity (unless you’re mission critical) Consider the following
211. Anticipate your user You’re on Wi-Fi Consider the following
212. Anticipate your user You’re on Wi-Fi: - Bad idea = update ALL!!! Consider the following
213. Anticipate your user You’re on Wi-Fi: Bad idea = update ALL!!! - Good idea = update more Consider the following
214. Anticipate your user You’re on Wi-Fi: Bad idea = update ALL!!! - Good idea = update more (ONLY what you’ll use) Consider the following
215. Anticipate your user User running in the park w/ headphones Consider the following
216. Anticipate your user User running in the park w/ headphones: - Good idea = start playing a playlist Consider the following
217. Anticipate your user User running in the park w/ headphones: Good idea = start playing a playlist - Bad idea = fetch data for a news app Consider the following
218. Anticipate your user Running+park+headphones = playlist Running+alley-headphones Consider the following
219. Anticipate your user Running+park+headphones = playlist Running+alley-headphones - Bad idea = start playing a playlist Consider the following
220. Anticipate your user Running+park+headphones = playlist Running+alley-headphones: Bad idea = start playing a playlist - Good idea = loud alarm Consider the following
221. Anticipate your user Running+park+headphones = playlist Running+alley-headphones: Bad idea = start playing a playlist - Good idea = loud alarm + speed dial police Consider the following
222. Questions?
223. “We should be building great things. Things that Don’t yet exist”
224. Hope you liked it Thanks for listening! Royi Benyossef (royi@samsungnext.com)