Partitioned Versioning Enables Risk-free Production Upgrades to Salesforce Mobile Apps

Traditional deployments of updates to mobile applications are hard, and harder still in the enterprise world. Mass, uncontrolled updates to users are risky at best. Partitioned Versioning, with MobileCaddy, enables a low impact, highly iterative, approach to application update deployments which minimises the risks.

Mobile applications need to be updated for many reasons. It’s common for an initial release of a new app to contain bugs that weren’t caught in sandbox and developer environments, for example, or for a misunderstanding of workflow to pass through the UAT stage unnoticed.

Beyond this, once an app is live and mature, it will still need to evolve in line with many factors including (but not limited to): new business requirements, regulatory updates, alignment with new OS and hardware capabilities, and of course in our world modifications to support new Salesforce releases.

Read more

October 2017: MobileCaddy Updates for Your Salesforce Mobile Apps

October_Update_Banner

Our readers have responded very positively to these monthly updates – this is our fourth now, for those who haven’t been following closely – on all the aspects of the MobileCaddy Application Delivery Framework (ADF) which are still being developed.

Over the past few weeks, our team has been hard at work adding even more new features to the ADF, further reducing the challenge of delivering Salesforce mobile apps for our clients and partners. It’s very encouraging to see the improvements and additions we make each month continue to prove useful, as we receive more requests and lots of great feedback.

So what’s new with MobileCaddy this month?

Read more