When I want an offline mobile application for Salesforce Should I use the Salesforce 1 Mobile app or the Salesforce Mobile SDK? Do I need Hybrid or Native? Which Salesforce Mobile Pack do I use? Can I encrypt device data? How much will our development cost? What development skills will I need?
Before MobileCaddy came along, our team had often faced these questions as well as the choices of which of these rich, powerful and awesome technologies we should use. We faced them one more time - when we created MobileCaddy. This is how it all began.
- Offline Data
- Offline Functionality
- Speed of Development
- Multiple Devices
- Fully Customisable UI
- Easy to Deploy
SF1 App Vs Salesforce Mobile SDK
The most obvious technologies to use are either Salesforce 1 Mobile Application or Salesforce Mobile SDK. Let’s gauge our requirements against them.
|Requirement||Salesforce 1 Mobile App||Salesforce Mobile SDK|
|Speed of Development||Yes||No|
|Fully Customisable UI||No||Yes|
|Easy to Deploy||Yes||No|
Mobile apps go offline - often due to a poor signal. Our apps must be available 24/7 in any location, be responsive and allow the developer to store their choice of platform data locally. We cannot develop the Salesforce 1 Mobile App and so we are pushed towards the Salesforce Mobile SDK which will allow us to develop around its gaps - ie development speed and ease of deployment.
"So we made our first decision....custom and offline won the day
Native Vs Hybrid
When developing with the Salesforce Mobile SDK you immediately are faced with a big decision point. We have application development options - Native, HTML5 or Hybrid. HTML5 apps do not offer secure offline storage so are not considered.
|Gestures Swipe, Pinch, Spread||Yes||Yes|
|Fast Graphics API||Yes||No|
|Secure Offline Storage||Yes||Yes|
|Native Look and Feel||Yes||Some|
Native apps offer the user that familiar look and feel with very responsive graphics - ideal for graphics intensive apps and games. However a Hybrid app only needs to be written once (with web development skills) and deployed to multiple platforms. A native app must be written once for each mobile platform (Objective C/Swift for iOS, Java for Android etc). The MobileCaddy choice here is for Hybrid apps - write once and deploy on multiple platforms.
"Tough call but we believe in HTML5 and love the idea of a single code base
Could we do better?
The MobileCaddy team developed very successful mobile applications for several customers once the decision to use Hybrid and Salesforce Mobile SDK had been made. Our choices above seemed sound! But we always want to do better! So one day we thrashed out a future project wish list - how could we improve?!
|Dev. Time||Variable depending on number of objects. Days to weeks in our experience.||Have working prototypes available in under a day|