Developing Offline-Capable Apps with the Salesforce Mobile SDK and SmartStore


Published on

1 Comment
  • Hi,

    I am developing a SmartStore android app. What I need to do is 'when my device goes from offline (not connected to internet) to online (connected to internet) then the data which I stored offline should get uploaded to salesforce automatically.

    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Developing Offline-Capable Apps with the Salesforce Mobile SDK and SmartStore

  1. 1. Developing Offline-Capable Appswith the Salesforce Mobile SDK andSmartStoreDeveloper TrackTom Gersic, Model Metrics / salesforce.comDirector, Technical Solutions@tomgersic
  2. 2. Safe Harbor Safe 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 of the assumptions proves incorrect, the results of, Inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our 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 or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other litigation, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This documents and others 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 be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available., inc. assumes no obligation and does not intend to update these forward- looking statements.
  3. 3. All About Model Metrics  Now a Company  10 year track record - 2,000+ cloud engagements  Passionate & innovative World-class skills - CRM,, Heroku, Radian6, Rypple, iOS and Android  In-house design studio – ModelFX  Mobile experts - iPhone, iPad and Android
  4. 4. Agenda • What we are going to build today • Salesforce Mobile SDK Overview • SmartStore Terminology and Demo • SmartStore Behind the Scenes • Building the app
  5. 5. What We’re Building Today, and Why
  6. 6. Offline Access
  7. 7. Offline Queuing
  8. 8. Backend
  9. 9. Salesforce Mobile SDK
  10. 10. Mobile SDK
  11. 11. Three Options: Which One Is Right For You? Advanced UI interactions Web developer skills Fastest performance Access to native platform App store distribution App store distribution Web developer skills Instant updates Unrestricted distribution
  12. 12. Hybrid Mobile App Development
  13. 13. Mobile SDK
  14. 14. Mobile SDK
  15. 15. OAuthAn industry standard method of validating user credentialswhile avoiding password anti-patterns.
  16. 16. OAuth 2.0 Flows Available User-Agent Flow Username-Password Flow SAML Bearer Assertion Flow Refresh Token Flow JWT Bearer Token Flow Web Server Authentication Flow
  17. 17. OAuth 2.0 Flows Available User-Agent Flow Username-Password Flow SAML Bearer Assertion Flow Refresh Token Flow JWT Bearer Token Flow Web Server Authentication Flow
  18. 18. OAuth 2.0 User-Agent Flow
  19. 19. OAuth 2.0 User-Agent Flow
  20. 20. OAuth 2.0 Refresh Token Flow
  21. 21. Oauth 2.0 and the Mobile SDK
  22. 22. Representational State Transfer (REST)A stateless data transport based on standard HTTPmethods for delivering data as JSON or XML
  23. 23. REST API HEAD is used to retrieve resource metadata. GET is used to retrieve information, such as SOQL Queries using SELECT. POST is used to create a new record. PATCH is used to update or upsert a record. DELETE is used to delete a record.
  24. 24. REST API Returns a JSON Response/services/data/v24.0/query/?q=SELECT Id, Name, Username__c, Password__c,URL__c FROM Password__c
  25. 25. Mobile SDK SmartStore SQLite ORM wrapper for Native and Hybrid apps built on the Mobile SDK NoSQL style JSON-based document store
  26. 26. SmartStore Stack
  27. 27. Smartstore Security Only cross-platform NoSQL mobile database technology on the market that comes with encryption built right in. And if you’re doing a hybrid (Phonegap) app…
  28. 28. WebSQL
  29. 29. IndexedDB
  30. 30. PhoneGap Storage Class
  31. 31. Native Database Technology Encryption • Encrypt your data yourself using PIN / Passcode • CoreData/SQLCipher  NSIncrementalStore  Good Dynamics • FMDB/SQLCipher  Salesforce Smartstore
  32. 32. Terminology Soup – is a database table used to store JSON documents with index columns. Soups are held in Stores, which are SQLite database files. This is all Apple Newton terminology  It had no real filesystem, so data was stored in database entries called “soups”  For the interested: • •
  33. 33. 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
  34. 34. IndexSpec • JSON Object • Fields to index • “string” or “integer” [ {"path":"Id","type":"string"}, {"path":"Name","type":"string"} ]
  35. 35. 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]%’”
  36. 36. SmartStore Demo Follow along with
  37. 37. SmartStore Behind the Scenes
  38. 38. Code Walkthrough
  39. 39. Tom GersicDirector, Technical Solutions – Mobile @tomgersic