Mobile platforms and mobile-specific features

What are the mobile-specific features of my app?

You should not expect to see a spreadsheet in your app. Your spreadsheet is only a data source. You are creating an app optimized for a mobile device in four ways: data presentation, data capture, offline use, and branding.

  1. Mobile devices have limited screen sizes, so each data row is presented using mobile-optimized patterns.
    • Most data views are summary views that expand to show the full details when an entry is clicked/tapped.
    • In summary views, we always show the key value and as many other columns as possible.
    • Actionable values (that launch actions when you tap them) like phone numbers and emails are preferentially shown.
    • Columns on the left of the spreadsheet are considered more important than columns on the right.
  2. Mobile-appropriate input controls are provided for different column data types.
  3. Apps that require connectivity and constantly utilize the network significantly reduce battery life. AppSheet apps are designed for offline access with only occasional synchronization over the network. The data used by the app therefore is cached locally on the device. This does constrain the volume of data that can be used in an app-- for this reason, in the current version of AppSheet, avoid extremely large spreadsheets. All updates on the device are made locally and pushed to the backend spreadsheet only during synchronization.
  4. Each app can be branded in a variety of ways, including with a logo. When you distribute your app to your users, you will control the brand experience for your users.


What mobile platforms do you support?

AppSheet apps run on iOS and Android devices in a variety of device form factors.


We require iOS version 9.0 or higher. We recommend iOS version 10.0. Earlier versions of iOS can cause subtle bugs or performance problems. 


We require Android version 4.4 or higher. We recommend Android version 5.0 or higher. Earlier versions of Android can cause subtle bugs or performance problems.

The memory required depends on:

  • The amount of data downloaded to the device. This depends on the number of tables and the number of rows and columns in each table.
  • The complexity of the app. This depends on the number of tables, views, expressions, etc.
  • The device features used by the app. The camera and scanner add significantly to the RAM required. The higher the camera image resolution, the more memory required.

If you are purchasing an Android device for use with AppSheet, we recommend choosing Android 6.0 or greater with at least 2GB of RAM. More memory may be required depending on the number and resolution of photos you capture. We recommend testing your app thoroughly on the device before committing to it. Android performance can vary significantly between devices with seemingly similar specs.


Can the apps run in a mobile (or desktop) browser?

Yes. While we primarily focus on mobile devices, some AppSheet customers also run their apps in a web browser, usually within an iframe. In fact, on unsupported mobile platforms like Windows Phone, we recommend running within a browser. Most of the app functionality is supported in a browser except for:

  • Bar code scanning
  • Offline image and document caching
  • Offline app launch 
  • Some upcoming functionality (like push notifications).

To run the app fullscreen in a browser, use the url:{app-id} . To use the app within an iframe, read this article.

We recommend a modern browser and the apps work best on Chrome. AppSheet does not work on Internet Explorer versions lower than V10.0. 

Have more questions? Submit a request


Article is closed for comments.