Native App or Web App? Follow
What is the difference and what is best to use in what situation?
Many of our customers have asked us what the difference is between the Native iOS app and the Web App version of our app. So we have detailed this comparative guide to help explain the benefits of each as well as outline how they differ.
| Feature | Native iOS App | Web App |
| App loading | Requires download from the iTunes store. (iPhone Only) | Available directly within a web-browser, no download required. (iPhone/Android) |
| Offline Mode (No need for internet connection) | Has the ability to function without an active internet connection for the device. | Relies on an active internet connection in order to provide content (Audio/Images/Video). |
| iBeacon Support | Supports iBeacon alerts. | Cannot support iBeacon alerts. |
| Software Updates | We push updates/fixes regularly to the Appstore. (Monthly) | We push updates/fixes regularly to the the WebApp. (Monthly) |
| Feature Updates | Feature updates will roll out first on the Native iOS App . | New features that are compatible with a web browser will be rolled out to the Web App in a delayed but timely manner. |
| Social Sharing | Supports Text/Email/Facebook/Twitter | Supports Text/Email/Facebook/Twitter |
| In App Alerts | Supports Geofencing/iBeacon Alerts. | Is unable to support geofencing or iBeacon Alerts. |
| Analytics/Tracking | Ability to generate visitor personas, as well as gather location/usage data. Also able to capture usage data such as which exhibits are most popular, which objects, and how long is being spent in each section. | Ability to generate basic usage data including which tours/exhibitions are viewed but unable to provide location data or user personas. |
| Image recognition | Supports offline/online image recognition. | No image recognition support. |
| In App Experience | Native applications have a more polished experience for the end user due to utilizing built in features on the iPhone to render and streamline performance. | Due to the limitations of the users web-browser the user experience will still be optimized however performance is limited to the browser type and device that is running it. |
| Donations | Can collect donations via the Native App. | Can collect donations via the Web App. |
| Memberships | Can can accept membership signups via the Native App. | Cannot accept membership signups via the Web App. (coming soon) |
| Accessibility Features | Natively supports iOS accessibility features including voice over and text size. | Natively supports accessibility features including voice over and text size. (Browser Dependent) |
| Map | Supports Indoor/Outdoor maps. | Supports Indoor/Outdoor maps. |
When does the Web App shine?
We have found that for single exhibitions with limited space and only one exhibition that will swap out often is better tuned towards the Web App. This is great for galleries that expect visit lengths of 10-15 minutes as it does not require the visitor to download the Native App.
When is the iOS app a more opportune solution?
For larger spaces or for multiple tours, we have found that the more immersive iOS Native App is the ideal solution for a visitor. It provides a more streamlined set of tours, as well as provides more value for a visitor who is spending 30 minutes to a few hours in a space. It also enables you to provide location based experiences and alerts that can help immerse the visitor in your space.
In Conclusion
We believe that providing both the iOS and Web App to your visitors is the optimal solution. Some people may wish to download the app and some wish to just use a Web App. From an engagement standpoint users who do download a Native App tend to have up to 20X the engagement levels of a browser experience and are much more likely to transact.
This is why we have bundled them together for you so you don't have to decide for your visitors!