Our MobileCaddy Trust site keeps our clients and partners assured that their mobile applications are running properly behind the scenes, with daily alerts and notifications. This article details a recent milestone reached by our systems, and also explains why we’re so happy to be wishing the Trust site a very happy second birthday.
With the release of the iPhone X, which has brought with it a new, larger screen size, Apple has also recently updated its App Store policy. This policy now requires all new submissions to the App Store to support the iPhone X’s display resolution. In this article we’ll detail the new requirements, explain how to comply with them, and also cover what impact this will have on MobileCaddy customers specifically.
Last month, the third annual edition of Europe’s largest community-led event for Salesforce professionals took place in London. London’s Calling is an event designed to bring together anyone working with Salesforce to network, share ideas, solve problems, and learn new things.
We were particularly excited about the event, as our Lead Mobile Technical Architect Todd Halfpenny was not only part of the team in charge, but was also presenting for the third year running.
The rest of the great organising and volunteering team was diverse, including Simon Goodyear, Kerry Townsend, Amanda Beard-Neilson, Francis Pindar, Jodi Wagner, and Lauren Touyet. We’re very proud of our contribution to these Salesforce community events, which also extends to our sponsorship of the London Developer User Group.
2018 was the best year yet
The event seems to be getting bigger and better every year, and 2018 promised plenty of interesting attractions and engaging sessions for attendees to get involved in.
Towards the end of last year it was revealed that 87% of Salesforce customers and 89% of Fortune 100 companies are now using applications from the Salesforce AppExchange.
This is great news, because it means that large enterprises are beginning to see the value in leveraging Salesforce’s multi-cloud and platform offerings as part of their digital transformation strategies.
These forward-thinking customers are now becoming more astute and, as a result, more demanding in their uses of this technology. But that’s putting huge pressure on Salesforce partners to deliver challenging projects at speed and without risk.
Business leaders also know they need a wide variety of supporting technology solutions too if they want to get the most value out of their multi-cloud infrastructures. That means Independent Software Vendors (ISVs) like us here at MobileCaddy, and Systems Integrators (SIs), are having to work together closely to ensure their Salesforce customers’ needs are being met.
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.
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.