Salesforce1 Access Considerations

By necessity, the Salesforce1 layout is different than the full Salesforce site layout you might be used to. Remember the following when creating a canvas app for use in Salesforce1.

• Since canvas apps are designed to display your third-party application inside of Salesforce, the device must have access to your canvas app URL. If your app is only accessible behind a firewall, the mobile device must be behind the firewall, too. If users don’t have access to the canvas URL, they receive an error—possibly a 404 or 500 error.
• When accessing your canvas app as an action in Salesforce1, if the canvas app uses the “What are you working on” header, the header is fixed at the top of the page and your canvas app scroll area falls below the header text box.
• The canvas app link and description in the feed might display fewer characters than what is displayed in the full Salesforce site.
• Depending on the device you use, the feed screen can change if the device is rotated. Your canvas app should support rotation if possible. Use the orientation event to handle changes in device orientation.
• The heights used in Salesforce1 and the full Salesforce site are different. Use the Dimensions object in the signed request to render your publisher actions correctly.
• In the action menu, long action labels might be truncated.
• The feed layout is different than that of the full Salesforce site. Instead of an app opening in the feed, a page opens that displays the canvas app on the entire screen. To return to Salesforce1, tap .
• When you view the action bar or Feed in Salesforce1, the default Force.com Canvas puzzle icon displays for canvas apps. You can override this default icon with an image you provide.
• When a canvas app appears as an option in the Salesforce1 navigation menu, the default Force.com Canvas puzzle icon is used. You can customize the icon in the connected app settings of your canvas app.
• Canvas apps aren’t available when the user accesses Salesforce1 offline.