In his article for metroConnections, Brad Neuman describes the various kinds of apps and their differences in order to help planners better select the app that is right for their event. Web apps require access through a browser, which can be difficult with a mobile phone. This is probably not the best choice because mobile users generally do not want to use the browser on their phones to get information. Native apps are actually downloaded to the mobile phone and the user can access the content without a network. Then, there are hybrid apps, which combine the features of the web app and native app. A native app works on any device, involves automatic download of information via a one time visit to a url, and is also usable offline (push notifications sent when able to access the internet).
Neuman then goes on to describe the criteria that must be considered before deciding on a type of app. One must think about the app’s purpose and what the user might want it for. The main factors he lists are data connection, user experience, community involvement, cost, design elements, content, and audience demographics.
Does the event site offer dependable WiFi? If online connection is an issue, it might be best to create a native or hybrid app. A web app is of no use if attendees have trouble accessing it. Also, these two kinds of apps are much easier to use. During times when the web cannot be accessed, the app will save the information and send it once there is a WiFi signal.
Cost is often one of the main determining factors of app use. It can be quite expensive to design a native app specifically for the event. Web apps and hybrid apps are less expensive. There are some development companies, however, that offer basic app design for a one time fee and meeting planners have the ability to throw together a custom app for each event using the platform. In addition, tech savvy attendees may expect a native app that can be used on their tablets or mobile phones，especially for the tablet owners as they are becoming the bigger users.
Before the hybrid app, CrowdCompass focused on native apps. With web apps, the entire success of the event depends on the venue's Wi-Fi service. All the event participators need to run the risk of not having adequate internet connection; attendees may not be able to view their schedules or other important information, speakers may end up presenting to small crowds, exhibitors’ booths may have no visitors, and sponsors may not stick around.
In contrast, a native app can avoid these risks, especially if it has more capabilities. It can have extra features like push notifications, photos, and location-based services to bring more value to the event and provide attendees with a more rewarding experience. Finally, native apps come with an architectural advantage in security, as they do not need to connect with the network as frequently as Web apps and, in some cases, skip the process altogether.
Now, the hybrid app becomes trend, but it is not mature enough and developers still need invest a lot of time on development. Event planner should try to provide both a native app and a hybrid app. it is not necessary to create a native app for every possible device though, according to the ratios vary by country.
Cvent gives some tips for making sure attendees are prepared to use either or both the native and web mobile event apps:
--Include “Download from iTunes” or “Download the Android App” icons on all your pre-event promotions and registration materials.
--Provide the name of your app.
--Provide the web address for the web-based version of your app, but encourage downloading of the native app for best results.
--As a mobile app best practice onsite, include obvious signage about how to access both the native and web-based apps in your registration area.Sources:
http://blog.cvent.com/blog/heidi-thorne/native-vs-web-mobile-event-apps-do-you-need-both
Contributed by Yumeng Xie and Ludell Maggard
No comments:
Post a Comment