Mobile apps 101 key patterns you need to know (webcast)
•Download as PPTX, PDF•
0 likes•1,698 views
We Will Discuss » - Recognizing common use-cases & design patterns from an array of mobile apps - Data services and technologies that power the server side of data-driven experiences - Assembling best-of-breed technologies to implement expansion into small(er) screens
Recommended
Recommended
More Related Content
More from Apigee | Google Cloud
More from Apigee | Google Cloud (20)
Recently uploaded
Recently uploaded (20)
Mobile apps 101 key patterns you need to know (webcast)
- 1. Mobile Apps 101 Key Patterns you need to know April 19, 2012 Ed Anuff @edanuff Greg Brail @gbrail Tim Anglade @timanglade
- 2. @edanuff @gbrail @timanglade
- 5. New! IRC Channel #api-craft on freenode
- 6. Use Case Design Pattern Identity Social Graph Show what’s happening Activity Stream Show what’s nearby Location as context Alert me! Push notifications Share info or state across devices Multipoint sync Access a service remotely The untrusted client
- 7. Identity
- 8. Identity Pattern: the Social Graph • Renting vs. owning • Value & Risk in both approaches – Management concerns – Privacy concerns – Reliance on third party services (& availability) • Friend, friends of friends friends of friends of friends…
- 10. Show what’s happening Pattern: Activity Streams • Personalized • Cross-references & Faceting • Duplication • Technical constraints are highly driven by UX expectations
- 12. Show what’s nearby Pattern: Location as context • Variant of Activity Streams? • Privacy Concerns, loss of resolution • Geocoding, reverse geocoding • Geo queries • Vectors & Ephemeral locations
- 13. Send me an alert!
- 14. Send me an alert! Pattern: Push Notifications • Stuff that can’t wait • Urgency is relative • Event not Content • Not meant for archive & retrieval • Wide vs. Precise
- 15. Share info or state across devices Source: apple.com
- 16. Share info or state across devices The pattern: Multipoint Sync • Used to be manual • Not easy • Invisibility is key • File or KV-based • What you have to handle vs. what you can’t handle
- 17. Share info or state across devices Also possible with Dropbox Nice tutorial by Nanaimo Studio: http://www.nanaimostudio.com/blog/2011/1/20/how-to-synchronize-your-app- data-using-dropbox-api.html
- 18. Access service from remote
- 19. Access service from remote Pattern: the Untrusted Client • OAuth all the way • Flows & options can be jarring to the developer • Flows & options can be jarring to the user • Revocation
- 20. THANK YOU Questions and ideas to: @edanuff @gbrail @timanglade
Editor's Notes
- Creative Commons Attribution-Share Alike 3.0 United States License