Developing Offline Mobile Apps with Salesforce Mobile SDK SmartStore

of 30 /30
Developing Offline Mobile Apps Tom Gersic Mobile Practice Director @tomgersic Follow along here!

Embed Size (px)


At some point, all mobile app users lose their data signal. Join us to learn best-practices for coding for offline requirements with the Salesforce Mobile SDK. We'll develop a simple app using SmartStore offline storage, highlighting the SmartSQL and SmartSync features. With these tools, you can take your mobile apps to the next level, developing native and hybrid applications on iOS and Android that have offline access to your data.

Transcript of Developing Offline Mobile Apps with Salesforce Mobile SDK SmartStore

  • 1. Developing Offline Mobile AppsTom GersicMobile Practice [email protected] along here!

2. Safe HarborSafe harbor statement under the Private Securities Litigation Reform Act of 1995:This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any ofthe assumptions proves incorrect, the results of, inc. could differ materially from the results expressed or implied by the forward-lookingstatements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or serviceavailability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for futureoperations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use ofour services.The risks and uncertainties referred to above include but are not limited to risks associated with developing and delivering new functionality for our service,new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions ordelays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers andacquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees andmanage our growth, new releases of our service and successful customer deployment, our limited history reselling products, and utilizationand selling to larger enterprise customers. Further information on potential factors that could affect the financial results of, inc. is included in ourannual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents andothers containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not bedelivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently, inc. assumes no obligation and does not intend to update these forward-looking statements. 3. Tom GersicMobile Practice [email protected] 4. What are we doing here? What we are going to build today Talk a little about offline Salesforce Mobile SDK Overview SmartStore Terminology SmartSync Terminology Walking through some code 5. I need this data, but my connection is awful!!! 6. Why offline? Go where your customers are. 7. Field Usage Analytics 8. What well build today 9. Google Polymer 10. Google Material Design Language 11. Polymer Hello World initbower install --save Polymer/polymerbower install --save Polymer/core-elementsbower install --save Polymer/paper-elementspython -m SimpleHTTPServerhttp://localhost:8000/ 12. Mobile SDK Customer Data 13. Three Options: Which One Is Right For You?Web developer skillsAccess to native platformApp store distributionAdvanced UI interactionsFastest performanceApp store distributionWeb developer skillsInstant updatesUnrestricted distribution 14. Its all about soup 15. Soups Hold Indexed JSON Documents JSON Responses can encompass data from multiple tablesId Soup Created lastModified Index 1 Index 2 Index N1 {JSON} 1371069899796 1371070436125 a00E0000009Xj2mIAC 2 {JSON} 1371069899802 1371070436126 a00E0000009Xj36IAC Facebook 3 {JSON} 1371069899803 1371129103154 a00E0000004h2MnIAI Google 16. REST API Returns a JSON Response/services/data/v29.0/query/?q=SELECT Id, Name FROM Contact 17. Soups and Stores 18. Some things you can do with your soup Register a Soup with an IndexSpec Query a Soup using a QuerySpec Upsert Data to a Soup Delete Data from a Soup Remove a Soup 19. IndexSpec JSON Object Fields to index string or integer [ {"path":"Id","type":"string"}, {"path":"Name","type":"string"} ] 20. QuerySpecbuildAllQuerySpec(path,order,pageSize)Query all records from the object in the given sort order (or null order)buildExactQuerySpec(path,matchKey,pageSize)Search for records with index path values matching the key.buildRangeQuerySpec(path,beginKey,endKey,pageSize)Return all records with an index path value between the two range valuesbuildLikeQuerySpec(path,likeKey,order,pageSize)Basically select * from [table] LIKE %[likeKey]%buildSmartQuerySpec(smartSql,pageSize)Basically select * from [table] LIKE %[likeKey]% 21. SmartSQLSELECT {departments:name}, {employees:lastName}FROM {employees}, {departments}WHERE {departments:deptCode} = {employees:deptCode}ORDER by {departments:name}, {employees:lastName} 22. SmartSync 23. SmartSync Extends Backbone.js Can be used with or without a SmartStore Cache Queries returned as Backbone Model Collections 24. Backbone MV* Framework Models: Individual records Collections: Collections of Model records View: Javascript backing for the stuff that you see Router: routes everything after the # in a URL to application functions 25. Force.SObject sobjectType: Account, Opportunity, etc. fieldlist: ["Id", "Name", "Amount", "StageName"] cacheMode: client, server write order mergeMode: how to handle conflicts cache: if using SmartStore cacheForOriginals: backup data for conflict detection 26. Force.SObjectCollection config: determines queries used to access data cache: if using SmartStore cacheForOriginals: backup data for conflict detection 27. Force.StoreCache soupName: Name of the SmartStore Soup additionalIndexSpecs: IndexSpecs to use, in addition to defaults keyField: Name of the field containing the record Id __locally_created__ __locally_updated__ __locally_deleted__ __local__ (set to true if any of the previous three are true) 28. Patterns for Offline Success 29. Offline Queueing