The Spring ’17 release is right around the corner. Spring ’17 is an exciting release for Salesforce1 because of a few changes we made behind the scenes that will dramatically increase performance for iOS users.

Based on feedback from customers and Apple’s recommendation, Salesforce1 is transitioning to WKWebView to provide an improved experience for Salesforce1 for iOS users. What is WKWebview you ask? WKWebView is an updated way to display interactive content inside of mobile apps.

This change is designed to provide a faster and more stable experience within Salesforce1 for iOS. The performance improvements will be amazing, we expect:

• 30% faster performance
• 70% reduction in memory usage
• Resolution of many long-standing web content known issues

Awesome, right? There is a small catch. Many of our customers have built workarounds (aka “hacks”) to improve the experience of the old UIWebview. This includes code to help with scrolling, button/field tap issues and other UI related problems. These workarounds will not perform as expected in Salesforce1 v12 since the WKWebview natively fixes these issues.

Don’t worry! We can help you identify if your org will be affected. First, if your org does not contain custom Visualforce pages no action is necessary. You get all of the performance benefits with a normal update.

If you’ve implemented workarounds in your custom Visualforce pages to deal with known issues with UIWebView, the transition to WKWebView may interfere with them. To ensure a smooth transition to Salesforce1 for iOS version 12.0, we recommend you test and review your current Visualforce implementations to identify any issues. Mobile Safari on iOS version 10 also uses the same web view as WKWebView so it provides an easy way to test. Prior to the official release of Salesforce1 for iOS version 12.0 you can test using Mobile Safari via the steps below:

1. Ensure you are using an iOS device running iOS version 10.0 or later.
2. Launch the Mobile Safari browser on your device.
3. Log into your Salesforce instance in Mobile Safari.
4. Observe the behavior of custom Visualforce pages, with UIWebView workarounds, and identify any issues under iOS version 10.
5. If you discover issues related to workarounds in your custom Visualforce pages on iOS version 10 or later, you should contact the developer of the page and tell them to remove or conditionalize the workarounds.

Alternatively, you can temporarily opt your org out of the transition by opening a case with Support.

For additional guidance on preparing for the transition to WKWebView, or for instructions on how to opt-out of this transition, see New and Improved Web View Available in Salesforce1 for iOS version 12.0.