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

Sealing Buy-In for Salesforce Mobile Apps with PoCs

Demand for sophisticated Salesforce mobile apps continues to rise. But any mobile project still needs to be approved, and pitching a mobile experience with UI mock-ups and PowerPoint slides won’t do your app justice. Whether you’re working internally or are a partner pitching to a client, a Proof of Concept (PoC) is a powerful way to demonstrate that an app can meet its requirements. This article will highlight the key benefits PoCs can bring, as well as examples and tips for maximising their impact.

Why bother with Proof of Concepts?

PoC applications are pivotal to any mobile app proposal, allowing the demonstration of fundamental concepts and principles. Including a PoC as part of a pitch is a great way to put something tangible literally in the hands of the decision makers. It’s an opportunity to reaffirm confidence to key stakeholders, particularly where critical technical requirements come into play.

 “The Proof of Concept system gives stakeholders a chance to understand the capabilities and limitations of the system.” - Anderson IT

A common scenario we’ve come across at MobileCaddy is the desire of our partners to reassure clients that fully network resilient mobile apps for Salesforce are possible. This example is also applicable to internal development teams working in larger organisations.

Our experience with offline-first architecture has proven this to be a grave concern for enterprises. As such, a PoC demonstrating exactly this functionality has been fundamental in progressing conversations beyond these sticking points, and further onto the real topic of how value can be gained from taking Salesforce operations mobile.

Read more

How MobileCaddy Keeps Your Custom Mobile Apps Running Through Every Salesforce Release

This article will detail the monitoring and testing processes MobileCaddy has in place to ensure mobile applications continue to perform through any environment changes, including the Salesforce releases which occur three times each year.

sf_release_cycle

An overview of Salesforce releases

Three times per year, a major Salesforce release occurs which introduces updates to its software. These releases happen automatically and affect everyone within the ecosystem, including regular customers and ISV partners with related solutions such as MobileCaddy.

These spring, summer, and winter releases are planned months in advance and are kept on a very precise schedule to allow for as much preparation as possible. The release cycle is made available to everyone, and Salesforce administrators are alerted via Salesforce’s own email alerts for admins.

Read more

Making the Right Choice for Mobile Salesforce Community Applications

The Salesforce Community Cloud allows organisations to bring together employees, partners, third-party workers, B2B customers, and even consumers. This article will explore three different approaches to delivering mobile Salesforce community applications, and will help readers choose the most suitable option.

Sf_Communities_banner

What is a Salesforce community? 

A Salesforce community is an online platform for organisations to connect employees, partners, and customers, while providing seamless access to the data and records they need to get work done or complete tasks.

community_cloud_rszBuilt on the Salesforce Community Cloud, they offer real-time engagement and the ability to share any file, data, or record anytime and from anywhere.

Read more