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.
In our latest monthly product update for customers and partners, we’ve concentrated on some of the ways in which the MobileCaddy Application Delivery Framework has improved to enhance the experience of building, operating, and supporting mobile apps on the Salesforce platform.
Once again, this discussion includes Paul, our CTO, Todd, our Chief Mobile Technical Architect, and Frank, our Lead Product Engineer. As always we cover the most exciting new additions to the MobileCaddy framework in the past few weeks
So what’s new with MobileCaddy this month?
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.
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.
The MobileCaddy Application Delivery Framework (ADF) continues to grow as we strive to give our partners and clients new opportunities to innovate with their Salesforce mobile applications. Catch up with the recent additions and releases to the ADF in our latest monthly update.
As always, I’m joined in this month’s discussion by Paul, our CTO, Todd, our Chief Mobile Technical Architect, and Frank, our Lead Product Engineer. Once again we talk through what exciting new features have been added to the MobileCaddy ADF over the past month.
So what’s new with MobileCaddy this month?
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.
Why is self-registration important?
The Salesforce Community Cloud is a way to connect both external users (such as customers, partners, and third-party resellers) and employees to an organisation, creating a digital channel to access and interact with, at anytime and from anywhere.
Community members demand constant availability of the digital processes and tools within, with emphasis on the self-service aspect of a mobile community experience offering the flexibility which creates real value for those users.
That self-serving nature can be improved further by adding the possibility of mobile Salesforce community self-registration. This removes a long-winded registration process, making the user’s digital engagement with the organisation even more seamless.