Salesforce Mobile App Rollout: Test Your Mobile Customizations

Admin Intermediate > Salesforce Mobile App Rollout > Test Your Mobile Customizations

When you’re finalizing your mobile customizations, keep these tips in mind:

  • Less is more. For your page layouts, consider the screen size of mobile devices and move the most important information to the top. Only add the fields that are truly necessary. A best practice is to include five fields or less on a page, and definitely no more than eight.
  • Build for speed. Think about performance when adding custom elements to your pages. Are there images or processes that can cause slower page load times? Users are less patient with performance on mobile devices, so streamline your content and keep your page elements as lightweight as possible.
  • Think about tap targets. Consider how users interact with their mobile devices when creating custom pages. For example, buttons are easier to tap than links.
  • Embrace mobile capabilities. Think about all the cool features available on our phones: location detection, camera, accelerometer, and more. Are there ways you can take advantage of the unique capabilities of mobile devices?

Test!Test!Test! Test with Pilot Users First!!!

Visualforce pages aren’t automatically mobile-friendly in the mobile app, and when you’re testing, you can have some issues with your existing pages and custom apps. You can either revise your code so that your pages work in the full Salesforce site and the Salesforce app, or you can create mobile-specific pages.

Yes, you love your Salesforce prodigies. But your rebels are just as important. You have to be prepared to hear all the potential complaints and pain points related to the use of the mobile app. And if you address those concerns early, you’ll turn your mobile rebels into your biggest cheerleaders.

Quiz +50

  1. For optimal usability, what is the preferred number of fields that you should include on a page that will be accessed from a mobile device?
    • A. 5 fields or fewer
    • B. 10 fields or fewer
    • C. 15 fields or fewer
    • D. There is no recommended limit. Mobile users don’t mind scrolling.
  2. What’s the proper way to test your mobile customizations?
    • A. Test exclusively on your own mobile device.
    • B. Test on every platform and device on which you intend to deploy.
    • C. Use the device emulators provided by Apple and Google.
    • D. Testing isn’t really necessary.
  3. How do you deal with a Visualforce page that isn’t behaving as expected in the Salesforce app?
    Visualforce가 제대로 작동하지 않을때 어떻게 해야하나?
    • A. Nothing, Visualforce pages automatically work perfectly in the Salesforce app.
    • B. Delete the page.
    • C. Revise the code, or create a mobile-specific version of the page.
    • D. You can’t use Visualforce pages in the Salesforce app.
  4. Piloting the app before you go live provides an opportunity to:
    • A. Validate your mobile use cases.
    • B. Delay the launch as long as possible.
    • C. Train your super users.
    • D. A and B
    • E. A and C

References

Vocabulary

  • spotty: 얼룩덜룩한
  • accelerometer: 가속도계
  • prodigies: 천재들
  • rebels: 반항아들
  • optimal: 최적의
  • usability: 사용성
  • sanity: 제정신