Royal Opera House

Mobile Culture

Old website

• Inflexible and costly to make changes

• Unstable, 30,000 error pages each month

• Frustrating customer experience, e.g.

waiting room

• Prevented the ROH from improving its

service and maximising income

Manual interlinking

Poor discoverability

1. Create ‘hub’ pages for the production

2. Migrate static to dynamic (data!)

Coherent and consistent linking

throughout the complete

production lifecycle

iPad

To App or not to App?

What we know

90% returning visitor shows users are engaged with the app (they are firing it up more than once)

Visits are roughly half the amount of downloads: Users are installing and upgrading, but not using on a daily basis. It’s likely they are using primarily when there is an interest in purchasing tickets through the app.

Most users are viewing productions. Some interest in news and videos.

Game anyone?

Open Data

The Future

• Ubiquitous platform

• Responsive Design

• Device influence

– The Death of BlackBerry?

– Market entrants

• Kindle fire

• Windows 8 Tablet