Brooklyn Museum Mobile Web on iPhone and Droid

Today we are releasing apps for both iPhone and Droid that, simply, wrap our mobile website.  If we have a mobile website, you may be asking why we felt we needed to release apps that basically do the same thing.  The answer is both simple and complicated.

Let’s look at our overall strategy for a moment.  Given the museum’s community-minded mission, we aim to spend our time developing content in a sustainable and accessible manner.  This means closely adhering to web standards and writing code and designing interfaces that play nicely across all platforms.  So, the first iteration of our Mobile Web launch was simple—hit www.brooklynmuseum.org on a mobile device and get redirected to a version of the site that renders well on (many) small screens.  Rather than create an app, we followed our strategy and developed so we didn’t need one, but everything can change quickly when you put people in the mix…

In order to launch our mobile site, I hosted a mobile meetup at Target First Saturday.  The purpose of the meetup was to get visitors started using Gallery Tag! and gain some feedback on the new game, but I was stunned at what happened as I met with folks.  Nine times out of ten, the owners of the devices had confused looks when I said, “open your web browser and go to www.brooklynmuseum.org.” I was floored at how much confusion was created just simply getting people to open their mobile browser.  Once we’d get through that, the idea of bookmarking it to the home screen was even more foreign.  At almost every turn, visitors were expecting an app.  Seeing these exchanges, I started to think about accessibility again. Of course, there’s the nuts and bolts web accessibility approach that we’ve been very committed to, but there are also accessibility issues around natural usage behavior.  In this case, it was clear to me that people on app phones wanted apps, not necessarily mobile websites and by not giving them an app, we were actually making it more difficult for them to find our content.

Android_Logo.png AppStore_logo.jpg

And, here we are.  We hired Dave Wilkinson to build apps for iPhone and Droid.  If you don’t know Dave, we knew him from his work on the Indicommons app and, besides that, he’s Flickr famous.  The apps are designed to simply wrap our existing mobile web site, which makes the endeavor sustainable for us.  We can continue to add content to the mobile site, but the apps themselves can stay static and this means we can avoid future development costs.  While we are not expecting downloads by the gazillons, we are hoping that this makes our mobile content accessible via as many avenues as possible.

Author profile

About Shelley Bernstein

Shelley is the Chief of Technology at the Brooklyn Museum where she works to further the Museum's community-oriented mission through projects including free public wireless access, web-enabled comment books, projects for mobile devices and putting the Brooklyn Museum collection online. She is the initiator and community manager of the Museum's initiatives on the social web. She organized Click! A Crowd-Curated Exhibition, Split Second: Indian Paintings, and GO: a community-curated open studio project. In 2010, Shelley was named one of the 40 Under 40 in Crain's New York Business and she's been featured in the New York Times. She can be found biking to work or driving '74 VW Super Beetle in Red Hook, Brooklyn with her dog Teddy. ::contact::
Filed under: Technology
Tagged: , , ,
Bookmark the permalink

4 Responses to Brooklyn Museum Mobile Web on iPhone and Droid

  1. Kianga Ellis says:

    Really interesting data on people’s familiarity with the web browser. Weird! Any hope on the horizon for Blackberry users? We’re not stricly business, but want access to art too!

  2. Hi Kianga,

    I’m afraid with Blackberry there are a whole other set of issues that we have to deal with, which make it almost impossible for us to develop properly for that platform given the small staff that we have. Pretty much any mobile browser that’s been built around WebKit will work. Blackberry is one of the few devices on the market that does not utilize it, which means we’d have to do a lot more dev work to get the site to render properly. In addition, one of the things that I noticed at the mobile meetup is that the web browser is not even standard within the Blackberry line! Every time a new person with a Blackberry would step up, I’d cringe to see the way the site rendered – on some newer devices, it would be (mostly) fine…older devices were a disaster, but almost every BB device I saw that night rendered differently. It’s sort of at this point, we just have to throw in the towel, I’m afraid. Here’s to hoping they start to standardize – it would make our jobs a lot more doable.

  3. Carl says:

    I like to use the ipad, but I would like to know how much different is the experience of looking at an artwork from an ipad? How can that be more interactive than an “in person” experience with the artworks? What is your point of view on this issue? Are you afrid that visitors will not come to the museum anymore?

  4. Hi Carl,

    I think you’d find this blog post helpful.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

4 Reactions

  1. Pingback: Sydney Design has an iPhone app

  2. Pingback: All in hand: Working with handheld devices conference | Cogapp

  3. Pingback: Museum Apps – Vorreiter sind Kunstmuseen - Sammlungsdinge

  4. Pingback: Museum Android App Gap – More thoughts and a response