Monday, 9 February 2015

What is Salesforce Mobile SDK 3.1 & Why to use it?


Quick characteristics of Salesforce Mobile SDK 3.1: 
  1. It is unified app architecture (SmartSync API for fast and responsive apps) brings unparalleled flexibility meaning that you can built hybrid or native apps using same core set of functionality regardless of their target platform. 
  2. Salesforce Mobile SDK 3.1 does have everything consistent like all the libraries, all the APIs & all the major mobile building blocks.
  3. Extended choice of development tools or UI frameworks like for iOS you can now use CocoaPods. So, with the Salesforce Mobile SDK 3.1 release, mobile developers no longer have to make these trade offs for selecting a preferred technology.
  4. Salesforce Mobile SDK 3.1 have flows to initiate authentication with an enterprise certificate.
Something Developers need to keep in mind!
  1. iOS 7 is now the minimum OS version for developing your iOS apps on the top of Salesforce Mobile SDK 3.1.
  2. For Android, min version required is 4.2.2 - API_17
Unified SmartSync APIs : This gives "Bulk Sync Routines Executive" from the native layer, even in hybrid apps with a new SmartSyncPlugin for Cordova apps. It also helps for full CRUD operations for online and offline usage.

CocoaPods for iOS : Developers now have the ability to consume the Salesforce Mobile SDK through CocoaPods, which makes dependency management a chore of the past. It’s now easier than ever before to insert Salesforce Mobile SDK modules into an existing app or evolve a new app with other third party libraries.

Gradle for Native Android Apps : Android Studio and the Gradle build system are now fully supported for native apps.  Gradle support for hybrid apps will arrive after the next Cordova update.

Certificate Based Authentication Pilot : Leverage certificates as part of an enhanced authentication flow without asking your users to enter a username and password.
Posted by at No comments:
Subscribe to: Posts (Atom)