How I left iCloud

An introduction to my first iOS app, its use of iCloud, and how it was migrated from iCloud to Firebase.

August 2013

Transcript

1. How I left iCloud
2. My first iOS app • Simple multiple list task manager • Written in Objective-C • Developed using Xcode • Uses Core Data and iCloud
3. Questions • How to support multiple devices • How to perform database migrations
4. Core Data and iCloud
5. Core Data • Apple's abstraction of underlying database technology used in iOS and Mac OS X • Developers can model data architecture; Core Data does all the legwork • Supports migration of database (e.g. to add a due date to all tasks)
6. Problems with Core Data • Modelling is a pain 1
7. Problems with Core Data • Draw models and relationships • Multiple versions of specification (e.g. to support migrations) • Disassociated from the actual code 1
8. Problems with Core Data • Database migrations 2
9. Problems with Core Data • Database migrations aren't always easy • Sometimes extra code needs to be written 2
10. iCloud • "Seamlessly" synchronise documents and databases between multiple Apple devices • Fairly easy to implement, but this depends on the requirements of each application
11. Problems with iCloud • If it goes wrong.. • ..reinstall application! 1
12. Problems with iCloud • Poor error messages for developers • No access to any user's data 1
13. Problems with iCloud • Can't test on iOS Simulator • Synchronisation takes an unspecified period of time 2
14. Solving the Problems: Core Data
15. Remember NoSQL? • Schema-free • Easy replication • Simple API • Eventual consistency • Humongous data
16. NanoStore https://github.com/tciuro/NanoStore
17. NanoStore sqlite
18. RubyMotion!
19. NanoStore sqlite NanoStoreInMotion https://github.com/siuying/NanoStoreInMotion
20. Main benefits • No modelling required, just code and go • The model is the code • No need for simple migrations
21. NanoStore sqlite NanoStoreInMotion Sadis Server for application and device independent database synchronisation
22. Example class Task < Sadis::Model attribute :parentID attribute :title attribute :displayOrder attribute :completed attribute :sequenceID belongs_to :list, "List" class List < Sadis::Model attribute :title attribute :displayOrder has_many :tasks, "Task"
23. Solving the Problems: iCloud
24. Write my own replacement!
25. That's not stupid
27. Time passes..
28. Then I discover..
29. What is Firebase? • Key-Value pairs of data • Accessible at a given URL:
 e.g.: ../model/list/123 • Read, write, query
30. Why is it brilliant? • Libraries for iOS and Mac OS X, Android, JavaScript • Well documented and easy to use • Access rules • Clients can listen for live updates to data, and write live • Lightning fast • Built-in caching, so works offline • Developers can get access to the data
31. Updating Sadis • Enhanced to work with Firebase • Completely seamless • Any set of models work with Firebase, automatically
32. Multiple devices
33. Delivers changes to data
34. Maintains Firebase content automatically
35. Self-maintains
36. Simulator iPhone
37. Demo
38. What about the web?
39. Oodles of options • Official libraries that integrate with Angular.js and Backbone.js • Lots of unofficial libraries
40. after much trial and error... • backbone.js, using basic firebase.js library • marionette.js • Backbone.VirtualCollection
42. Demo
43. What next? • Add multi-user support • Update my iOS application accordingly • Write Mac OS X application • Write web application