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

How MobileCaddy Aids Bugless Salesforce Releases

We’re all aware of the thrice-yearly Salesforce releases, and how they’re unstoppable forces. We’re all also aware that bugs exist, and that any bug found post-launch is a lot more expensive than one found during testing. Here’s a quick story on one such bug, and how MobileCaddy helped to get it removed from the Winter ‘18 release.

Whenever Salesforce patches make their way into pre-release orgs our daily test runs kick off and identify the change. These tests run on 15+ org setups and report back any issues that might have been observed. One such observation was reported back during the early days of Summer ‘17 patch rollouts into pre-release. The issue manifested itself initially as the inability to complete the authentication flow on iOS devices built with Salesforce Mobile SDK v4.0.2 and lower.

During the investigations into the issue, we raised a notification on our trust site to keep our partners and customers aware of the risk of the behaviour. We also developed some internal work-arounds. If the issue wasn’t fixed prior to Summer ‘17 making it’s way into our partners’ sandboxes, these would let us unblock them from their development and testing processes.

We also discovered that the bug broke the vanilla experience of browsing standard Visualforce pages on iOS Safari; this could be bad if it got through into production.

Read more

How to Master Salesforce Mobile App Distribution with Containerisation Services

As the demand for custom mobile apps continues to skyrocket, it’s becoming easier to meet business requirements by using hybrid apps built with standard web technologies, and using container apps to overcome the challenge of distribution. This article provides an overview of how to easily distribute Salesforce mobile apps across iOS, Android, and Windows 10.

Hybrid Apps Open the Door for Containerisation

There are essentially two different approaches to building mobile apps: native and hybrid. It is important to understand the high-level differences to put this article in context to then see how we can leverage Container Apps to de-skill, de-risk and accelerate our time to market.

Read more

July 2017: What’s New with MobileCaddy and Your Salesforce Mobile Apps

The Latest from the MobileCaddy Product Team - July 2017

One of the most exciting things about our Application Delivery Framework (ADF) is that it’s constantly growing and evolving, to allow our partners and customers to push the boundaries of what can be achieved with mobile apps on the Salesforce platform. As such, it’s vital that we help our community stay abreast of all the new MobileCaddy features and updates as they’re released.

With that in mind,  I’ve decided to record and publish my regular discussions with Paul, our CTO, Todd, our Chief Mobile Technical Architect, and Frank, our Lead Product Engineer. In these sessions we’ll be covering what’s new with MobileCaddy, and will be sharing this with you to provide a first-hand look at everything we’ve been working hard on to improve.

So what’s new with MobileCaddy this month?

Read more

Keeping Your Salesforce Mobile Apps Working Through OS Version Updates

Changes frequently occur to mobile operating systems outside your control, and your awareness, which can cause serious problems for your applications. When those apps are supporting critical business processes, it’s vital you’re constantly testing to ensure their performance is never compromised. This article will outline an approach to prevent OS version updates, upgrades, and other environment changes from affecting your enterprise mobile apps.

 

Apple_AndroidOperating and supporting any enterprise application in the context of mobile is challenging, because you don’t have control over that app’s underlying operating systems, nor can you predict new updates, upgrades, or patches being released.

This presents a problem for those responsible, because changes to an OS can cause mobile apps to suffer in their performance, or even stop working entirely. When those apps have been deployed into functions which are critical to the daily running of the business, that effectively renders the employees or community users relying on the app incapable as well, which simply can’t be allowed to happen.

So, firstly… Understand your app

You need to be aware of all the various components which make up your application, how they interact with each other, and what relationship they have with the OS.

Any number of things within your app can change without your knowledge, and the various elements and supported systems mean that continual testing is an absolute necessity to avoid app failure. This becomes even more important when applications are supporting business critical processes and workflows.

Read more