This month MobileCaddy were among great company as proud sponsors of the first ever London’s Calling – The biggest Salesforce community event in Europe! And what a brilliant event it was to.
There were six of our team attending the event (including our Mobile Technical Architect who presented a talk there) and it is testament to the organisers that we were all in conversation with attendees from the minute we arrived until late into the evening. The fact that all of these chats revolved around how to make their own or their clients organisations more successful was even better.
Now that the dust has settled we have had time to review all the interesting conversations we had as a Sponsor/Exhibitor. So it seems as good a time as any to dig into the 3 most common themes of the great questions we were asked by the community.
What is a critical mobile app?
There was a tremendous amount of interest in understanding what a critical mobile app is and why it would matter to a Salesforce customer. This question drives at the heart of what MobileCaddy delivers – the ability to confidently mobilise mission or business critical apps using the Salesforce platform.
The easiest way to understand what is, and what isn’t, a critical mobile app is to ask one question. If the app stops does this stop the business delivering or creating value?
For example if it is a community app would the customer not be able to raise support tickets or place orders? If it is an employee app would the sales rep not be able to process an order? (to see the design principles we use to ensure an app is suitable for critical processes check this earlier post)
So at this level a critical app is very easy to define. In fact we would argue that if a mobile app is not critical there would be a question mark on why it was deployed in the first place.
Now, to keep this app performing day after day brings us to the next popular discussion we had.
What is a Critical Lifecycle System?
A number of partners, developers and end users told us stories on how a mobile app that they had deployed or used themselves had very quickly encountered issues. The discussions we had around what a Critical App is (see above) also led on to the what makes an app continue to perform.
In both these cases there was a lot of interest in what a critical lifecycle system is and what it can do.
The success of an app is not when it is deployed. It is not even after six months. It is how the app performs and continues to deliver business value day after day after day. To ensure this is possible with the least amount of cost and overhead a MobileCaddy developed application sits inside a Critical App Lifecycle system (see below) that ensures success is baked in from the design process and continues through each step of the application lifecycle.
This means we can all feel confident that the app can live through changes to mobile OSs and changes to business processes, that every instance of the app on every employee or customer device is monitored and provides valuable analytics with no extra effort. And that once these analytics or new business processes are defined these can be added into the App through a simple versioning process, complete with targeted user testing.
All of this is to ensure maximum app uptime – which maximises the value being delivered to the business and ultimately the customer (this is all delivered in a single native force.com package right from the AppExchange)
Why is the Mobile Cloud different from the Cloud?
OK – so we are paraphrasing a bit here – but the questions around why mobile is such a different beast, all really have the same answer.
Once ‘Offline First’ is agreed as core principle of any mission or business critical app then we quickly see that there are then four critical differences between the way apps are delivered via the ‘Cloud’ (think Salesforce in the browser) vs how a Salesforce custom app is delivered confidently to a mobile device
A more in depth explanation is available in this earlier post but the key conversations we had with attendees here was that is is very important to understand that connectivity, data duplication, deployments and versioning are all new considerations when going mobile.
Oh and an a side note here why Offline First should not be confused with offline, occasionally connected or occasionally disconnected was a point raised during these chats. It may seem like semantics but an Offline First approach if taken well is an important step in any critical mobile app.
It’s a wrap
As well as manning our booth we also spoke at and attended talks, met with other exhibitors and came away from the day generally more informed and more connected and of course excited to start working with many of the people we met.
Thinking about business critical mobile apps?
Schedule a time with an Enterprise Mobility Specialist to chat about your specific needs