Recommended
More Related Content
What's hot
What's hot (15)
Viewers also liked
Similar to Android client architecture – part 2 key takeaways
Similar to Android client architecture – part 2 key takeaways (20)
Recently uploaded
Recently uploaded (20)
Android client architecture – part 2 key takeaways
- 1. Android client architecture – part 2
- 2. Previously on Android Client Architecture
- 4. Once upon a time...
- 5. Why do we need a refresh button?
- 9. Questions we asked Why did the user download the app? To read news. To watch videos. What to show? What the user expects. What the user didn't know they could expect.
- 10. Content segmentation What's happening right now. Main headlines/ News splash News I'm interested in. General News. Videos.
- 11. Content segmentation – football app What's happening right now. Live score / commentary News I'm interested in. “Table” My fav team. General News.
- 12. What the user expects? What's happening right now Main title + News splash
- 13. What the user expects? What's happening right now Main title + News splash What's Hot
- 14. What the user expects? What's Hot
- 15. What the user expects? What's Hot Videos
- 16. What the user expects? What's Hot Interesting News What's Hot Videos
- 17. Let the numbers decide Nt = Navigation time. Fixed. Depends on my design Ct = Content time. Variable. Depends on the content.
- 18. Let the numbers decide Nt = Navigation time. Fixed. Depends on my design Ct = Content time. Variable. Depends on the content. Min(Nt / Ct)
- 19. What the user did not know he can expect?
- 20. Text to Speech News Flash / Live score.
- 21. Text to Speech News Flash / Live score.
- 22. Text to Speech News Flash / Live score. Only while driving.
- 23. Text to Speech News Flash / Live score. Only while driving.
- 24. When / How to update?
- 25. BG Update What's Hot BG Update Interesting News Other
- 26. BG Update What's Hot BG Update Interesting News Other GCM Embedded
- 27. GCM Embedded GCM Message can carry 4K payload. Enough for: Title Subtitle Dimestamp Image(s) URL(s) Use Multicast to send to all users.
- 28. GCM Embedded Zero latency What's hot is always up-to-date. No loading time Offline
- 29. BG Update What's Hot BG Update Interesting News Other GCM Embedded GCM + Back-off
- 30. Inactivity Back-off Update at periodic interval Only if received GCM notification. Double the interval for every redundant update
- 32. BG Update What's Hot BG Update Interesting News Other GCM Embedded GCM + Back-off Daily / Bundled
- 33. Batch & Bundle updates. Use SyncAdapter to handle all transactions Takes care of offline state. Easy to implement
- 34. What's Hot Back-Off App launch Server Interesting News Sync Adapter GCM
- 35. What's Hot Back-Off App launch Server Interesting News Sync Adapter GCM
- 36. What's Hot Back-Off App launch Server Interesting News Sync Adapter GCM
- 37. What's Hot Back-Off App launch Server Interesting News Sync Adapter GCM
- 38. Context Driver Updates Is the user standing or walking? Standing user is more likely to use the app longer. Change the pre-fetch amount & frequency accordingly.
- 39. Summary Use GCM to drive updates Use SyncAdapter to Batch and prefetch. Context is the king Which content is more important?
- 40. Summary What's Hot is always up-to-date Even if we don't have network when the user launches the app Most chances that “my news” / “my team” section as well. Zero latency when launching the app.
- 41. Happy Coding
Editor's Notes
- Who here is first GDG? Who saw / read the android client architecture?
- Displayed the quick, dirty and wrong Solution 1: service Solution 2: content provider Solution 3 – sync adapter
- I'd like to share with you a story / process that I've gone through, building the next version of an applicatin that may or may not exist, in a country that may exist but soon will be under attack. In a meeting we discussed newer designs and we talked about the action bar. We placed a share button, like button and refresh button, And then – someone in the room asked:
- My response: Well.. when the user want an updated data – he clicks on refresh and then we go and fetch... Everybody nodded ahhhh Then he asked: I thought the user ALWAYS wants the most updated data. The use case that you describe does not exists.
- We decided to kill the refresh button. RIP After some work we had a version with no refresh in it. But....
- OOPS – battery performance
- DOPE. We went back to the drawing board.
- In order to answer what the user expects we took a deeper look at our content
- We had an argue: some said the user expects to see videos, others said the user wants to see news in the fields that he is interested in.
- We had an argue: some said the user expects to see videos, others said the user wants to see news in the fields that he is interested in.
- We had an argue: some said the user expects to see videos, others said the user wants to see news in the fields that he is interested in. What do you guys think? Who thinks A? Who thinks B? We decided to go with the mathematical approach
- We decided to go with news that I like and not videos. The next question:
- Basically there are two types of updates: 1. FG 2. BG I'm gonna talk about BG only, as FG is edge case of BG. Intense research showed that the changes are at server side. Hence – it will make sense to have server trigger updates.
- Three types of updates: What's hot / Interesting News / Other What's hot – research shows that the change is on the server side ==> Server Trigger. Server Trigger == GCM
- Like before: Server trigger. Let the client adjust the update frequency and not update for every change ==> Be more efficient
- Batch: If I touch the network – Fetch “other” as well. If not – not.
- So – our components are...
- We can improve even more with fine grain pre-fetch and batching by being more contextual