For some time I've been interested in getting a snapshot of the state of the technical implementations of mobile websites in higher education. Last week I tried to pull some numbers together on that topic for my talk on HigherEd Live. If you're interested in more "management"-type questions Karine Joly (@karinejoly) is currently running a survey to get answers to those. Take some time to help the rest of higher ed out by answering a few questions. It doesn't matter if you have a mobile higher ed site or not!
For this survey I reviewed institutional mobile websites for schools listed in my Higher Ed Mobile Directory. By "institutional" I mean that I ruled out purely marketing-focused sites like the WVU Today Mobile Experience and library mobile sites. Institutional mobile websites are meant to provide services to an entire campus and not just a small segment of the population. To help populate the Higher Ed Mobile Directory I used a list of US-based schools granting bachelor or advanced degrees and ran an automated check of popular mobile web addresses against it. Because of this my directory is seriously lacking in international schools. So take this survey as a primarily US-centric view of the mobile higher ed world. For the international folks checking this out… sorry.
Time to run through the questions I wanted answered…
How many institutional mobile websites are there and how does that number compare to the overall number of higher ed websites?
Based on my initial list of 1,789 schools it looks like only 160 or 9% of schools have an institutional mobile website. Mark Greenfield (@markgr) pointed me at the Carnegie Classification which currently tallies a whopping 4,600+ higher ed institutions. Sadly, it doesn't look like I can easily get web addresses for all of them to test against.
What solutions did schools use to develop their mobile websites?
This is a tricky number to come up with because I don't really know what they used. Because of that there is a very large "Homegrown/Unknown" bucket with 71% of the total. I do think it's fair to say that those schools attempting to get a mobile presence setup are going on their own. Blackboard was the most obvious vendor product and the largest single solution used with 15% of the total. Mobile Web OSP was the second most used solution at 8% and MIT derivatives other than Mobile Web OSP rounded out at 6%.
One interesting thing to note about Blackboard and the mobile web is that a school like Stanford has a Blackboard-based mobile site and a separate, homegrown mobile website. The Stanford home page redirects to the latter so it's not like it's some dead, forgotten website.
What are the popular types of content?
Looking at the results I can't say I'm too surprised. News (on 87% if the schools surveyed), events (78%), and directory (76%) are probably the easiest sections to get a mobile version up and running for. I'm a little bit disappointed by the showing for maps (65%). If you're going to develop a mobile solution a good map is a must. I do understand the difficulty in getting data but mobile is all about location. A few things that I expect to work into our own mobile site based on the results are: a note about our text alert system on our mobile emergency page, higher visibility for links to our email platforms, better search feature, and contact us and request info forms. All are low on the list but I think they do offer real value. This chart shows all sections that showed up on 10 or more higher ed mobile websites.
What web address should we use?
I would actually suggest to use all of these. At WVU we don't but I'm going to remedy that. Also, a few schools answer to multiple hostnames but I just included the first one I found.
For design layout which is more popular, grid or list?
There are basically two design layouts at this point in the higher ed world. The grid (31%) (e.g. like the iPhone homescreen) and the list (69%) where items are just stacked on top of one another. I personally prefer the grid layout. Shocker, I know.
How many device classes do these sites support?
One of the main features of Mobile Web OSP, Molly Project, and the MIT derivative frameworks is support to give custom layouts based on requesting device. In order to organize these layouts we refer to them as device classes (e.g. iPhone and Android in one device class and the Motorola RAZR and other features phones in another). I'm a little disappointed that their aren't more schools attempting to support at least two device classes (31%) but I guess that's understandable.
By the way, the most obvious single layout was one for the iPhone at 320px. Wish I had a separate question that categorized the designs I saw.
Do schools redirect mobile home page traffic to their mobile site?
I really think schools should do this. For the casual user trying to find mobile information their first stop is going to be the home page. Make it blindingly obvious where they can get mobile-optimized information by redirecting them. It'll be your biggest form of advertising for your mobile site. Always give them an opt out though.
Do schools provide a link to the mobile page on the home page?
We don't do this but I think it may be time to change that up. I was surprised by how many did.
Do schools provide a link from their mobile page to the home page?
This is a no brainer to do though it's surprising only 63% do so…
How "heavy" are higher ed mobile websites?
Which map solution is most popular?
I'm totally focused on the campus map. If you asked me which mobile content you should be developing I'd list campus map as #1 and trail it with a few exclamation points. Everything mobile comes back to location. I know I'm repeating myself but I figure no one has actually read this far by now.
What do schools used for mobile analytics?
One thing to note about mobile stats, we rely on both internal stats recorded in our database for the site as well as Google Analytics. Internal stats are most accurate but don't come with the depth of Google Analytics.
Are any schools using advanced features like geolocation?
Last on my list of questions are the serious technical issues like support for the HTML Geolocation API. While geolocation has been addressed by a couple of schools things like the local database or local/session storage are schools running Mobile Web OSP 2.0. I only checked media queries for the mobile sites and not home pages. I just didn't have the stomach to review 1,789 pages by hand though I could have spent some time and figured out an automated way to look at it.
Hopefully these numbers shed some light on the current state of the technical implementations of mobile websites in higher ed. It was a really tough slog to get all the data together and I don't relish the idea of doing it again but it definitely helped me understand what might be useful to push in the future. I hope it helps you too.