How to Keep Your Mobile Apps Running Properly Amid New iPhone X Requirement

iphonex_featured2

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.

Read more

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

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

How Non-Functional Testing Enables the Delivery of Defect-Free Salesforce Mobile Applications

All applications need rigorous testing, and non-functional testing is often viewed as the less important half of a whole when compared to functional elements. In reality, though, non-functional testing is crucial for creating a defect-free mobile app. This article will highlight the importance of initial non-functional testing and offer advice for carrying out the necessary processes.

non_functional_sizeIt’s common to focus on functional requirements and usability when testing an application, areas which are often where most of the effort is spent once an app has moved into the testing, QA, and UAT phases of a project.

Before even thinking about any functional app code, though, it’s important to test all the app’s non-functional elements first. If those aren’t prioritised, not only will it have a knock-on effect on all other testing, it will also impact the app’s ability to function once deployed.

Defining, and clearly understanding, non-functional testing processes is the key to releasing a defect-free mobile app into production. When separated into two groups, these can be referred to as ‘initial’ non-functional tests, and ‘running app’ non-functional tests. But before we go into more detail, it’s necessary to understand why non-functional testing is unique for mobile.

Read more