BYOD? - The #1 Consideration For Planning Mobile Device Interpretive Programs (To app or not to app)

Jun 25 2015

mobile museum appmobile museum appIn the last post to our Museum Exhibit Multimedia blog I wrote about the HUGE touch screens that are becoming so popular in museums and public venues.  Ironically, tiny screens are becoming popular at the same time.  I’m referring to the tiny screens that most of your visitors bring into the museum or venue in their pockets.  You may hear the term BYOD or Bring Your Own Device being used nowadays and it refers to programs or web sites designed for your visitors to access on their mobile devices.  Not convinced that you should consider this type of program?  Here are some statistics I’ve found on the web.  

Whether or not this convinces you to continue reading, at some point you’ll be faced with a decision whether or not to offer educational interpretive content to your visitors using these devices.   We’ve definitely seen interest growing with our clientele and have assisted in providing these types of content.  So what is the #` consideration to be aware of as you begin your journey?

To “app” or not to “app.”  An app (as we are considering it) is a program (or “application”) designed to run on a mobile device.  Typically it’s a program that is downloaded from iTunes or the Google Play Store and that resides on your device so you don’t need internet access to use the program.  The main alternative is a mobile friendly web site that offers the same or similar functionality.  Which is better?  Well, it really depends on your usage and resources but in my opinion there are many reasons to develop a mobile friendly web site for your mobile friendly offerings.

1.  Development costs (both time and money).  In order to develop an app that is universally available to all people with their different mobile devices, you actually need versions for every mobile operation system (OS).  So for Apple users you need an app developed according to Apple’s guidelines and programs and you need to distribute that program via iTunes.  For Android devices you need an app developed specifically for the Android OS.  These 2 programs are not compatible with each other.  Any other device types you want to support? There may be additional versions required.  This can be expensive.  If you go the route of a mobile friendly web site, that site can be developed to work universally on all devices.  One program, period.

2.  Maintenance.  With the speed of advancement in technology, either solution may require ongoing maintenance to ensure ongoing compatibility however, maintaining one program (your mobile friendly web site) is much easier and cost effective than maintaining several app formats.  So when the new iPhone comes out, you may be required to update your Apple app.  Then when Samsung fights back with their new device you may need to update your Android app.  And on and on it goes.  With a mobile friendly web site the format changes occur much less frequently and you are updating for all devices at once.

3.  Additional usage opportunities.  Your mobile apps can be used only on devices running the OS they were developed to support.  Your mobile friendly web site is designed to be used in a web browser (yes, any including Chrome, Safari, Firefox, IE, etc.).  So as a benefit, not only can mobile devices access your mobile friendly web site, desktop computers can also access and use these sites.  These site may not be set up to optimally use larger screens, but they can be used well if designed properly.  That just give you an opportunity to reach more people or reach the same people in additional ways.  That’s a win/win.

4.  Content updates and bug fixes.  Again, the more programs you need to update or fix, the more time and money it will take to update them.  If you are maintaining one mobile friendly web site all of your resources can be directed to that one effort.  

5.  Internet access.  This is the one consideration where apps have a small advantage over mobile web sites.  Although visitors will need web access to download your app, once it’s downloaded, they don’t need that web access to use the program.  A mobile friendly web site will require internet access to use the program.  The way our client at the Museum of Flight in Seattle satisfies this need is that they offer free wireless internet access to visitors.  More and more, public (and private) venues are offering wireless internet access so this may not be a big stumbling block as compared to the other considerations.

So as you can tell, I’m firmly in the mobile friendly web site camp although for clients who believe that apps are a better solution for them, we certainly offer app programming services.  

If you’d like to see an example of an online, mobile friendly web solution, take a look at this case study on the program we developed for the Museum of Flight.  http://www.exhibitfiles.org/online_app_for_the_museum_of_flight2

If you have comments or questions please comment here or give us a call or send us an email.

Chris Meyer
President
CD Meyer, Inc./point2explore
point2explore is product line of customizable touch screen kiosk programs including interactive games and informational programs.  point2explore products are currently running in over 100 museums and have been used in corporate events across the country. Visit our web site at http://www.point2explore.com.

  

Visit Our Web Site

Click Here to visit point2explore.com for touch screen kiosk software and products.

Exhibit Multimedia Blog

Minimize

Error: Object reference not set to an instance of an object.

In: at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.PermaLink(TabInfo tab) at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.PermaLink(Int32 strParentTabID) at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.GetProperty(String strPropertyName, String strFormat, CultureInfo formatProvider, UserInfo AccessingUser, Scope AccessLevel, Boolean& PropertyNotFound) at DotNetNuke.Modules.Blog.Templating.BaseCustomTokenReplace.replacedTokenValue(String strObjectName, String strPropertyName, String strFormat) at DotNetNuke.Modules.Blog.Templating.BaseTokenReplace.ReplaceTokenMatch(Match m) at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator) at DotNetNuke.Modules.Blog.Templating.BaseTokenReplace.ReplaceTokens(String strSourceText) at DotNetNuke.Modules.Blog.Templating.GenericTokenReplace.ReplaceTokens(String strSourceText) at DotNetNuke.Modules.Blog.Templating.Template.ReplaceContents()

Error: Object reference not set to an instance of an object.

In: at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.PermaLink(TabInfo tab) at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.PermaLink(Int32 strParentTabID) at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.GetProperty(String strPropertyName, String strFormat, CultureInfo formatProvider, UserInfo AccessingUser, Scope AccessLevel, Boolean& PropertyNotFound) at DotNetNuke.Modules.Blog.Templating.BaseCustomTokenReplace.replacedTokenValue(String strObjectName, String strPropertyName, String strFormat) at DotNetNuke.Modules.Blog.Templating.BaseTokenReplace.ReplaceTokenMatch(Match m) at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator) at DotNetNuke.Modules.Blog.Templating.BaseTokenReplace.ReplaceTokens(String strSourceText) at DotNetNuke.Modules.Blog.Templating.GenericTokenReplace.ReplaceTokens(String strSourceText) at DotNetNuke.Modules.Blog.Templating.Template.ReplaceContents()

Error: Object reference not set to an instance of an object.

In: at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.PermaLink(TabInfo tab) at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.PermaLink(Int32 strParentTabID) at DotNetNuke.Modules.Blog.Entities.Terms.TermInfo.GetProperty(String strPropertyName, String strFormat, CultureInfo formatProvider, UserInfo AccessingUser, Scope AccessLevel, Boolean& PropertyNotFound) at DotNetNuke.Modules.Blog.Templating.BaseCustomTokenReplace.replacedTokenValue(String strObjectName, String strPropertyName, String strFormat) at DotNetNuke.Modules.Blog.Templating.BaseTokenReplace.ReplaceTokenMatch(Match m) at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator, Int32 count, Int32 startat) at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator) at DotNetNuke.Modules.Blog.Templating.BaseTokenReplace.ReplaceTokens(String strSourceText) at DotNetNuke.Modules.Blog.Templating.GenericTokenReplace.ReplaceTokens(String strSourceText) at DotNetNuke.Modules.Blog.Templating.Template.ReplaceContents()

  
point2explore - Exhibit Multimedia Blog
Privacy Statement    |   Terms Of Use

Copyright C.D. Meyer, Inc. All Rights Reserved