Presentation at KULTUR PÅ NETT 2012 in Trondheim. The subject is Europeana's thinking and plans concerning development for mobile and its relation to our API-strategy during 2012 and the first half of 2013.
4. Specific Europeana metrics re: mobile
Mid-2011: iPhone 70% of our mobile users
• Android 2nd
• Blackberry, Symbian, Windows near-negligable
Latter half of 2011 onwards: quick rise in tablet
usage
Projected usage:
December 2011, 6% mobile (incl. tablets)
December 2012, 15% mobile (incl. tablets)
December 2013, 38% mobile (incl. tablets)
5. Choices: Native app vs. Web app
Mobile apps currently have better usability than
mobile sites, but forthcoming changes will
eventually make a mobile site the superior
strategy.
Jakob Nielsen
6. Choices: Native apps
Native applications advantages
• Better user experience
• Access to onboard devices and sensors
• Access to strong distributors (and payment models)
Native application disadvantages
• Fractured OS-market (Apple, Android, Windows, Blackberry)
• Demands diverse development skills
• Traffic in a silo outside of the web
• Conclusion: Build native apps if you are rich in
resources (money, internal development) and are
looking for intense user interaction including the device
sensors.
7. Choices: Web
Web advantages
• Develop once, maintain one platform
• On the web
Web disadvantages
• Sub-optimal user experience
• Standardised GPS access only, no other sensors
• Conclusion: Build mobile web if you have limited
resources, a small development team and are looking
for a user experience independent of device and
sensor access.
10. Mobile first and Responsive design
• Mobile first is a design philosophy that focuses
on progressively enhancing a site at increased
screen-sizes.
• Responsive design is a design technique that
presents site pages content as effectively as
possible at varying screen sizes
11. Development plans re:mobile
• Mobile first and responsive (re-)design of the
Europeana exhibitions and Europeana portal
• Ongoing
• Responsive (re-)design of Europeana 1914-1918
• Starting very soon!
• Any new Europeana web presence will be
developed according to the mobile first and
responsive design principles
• Geo-location aware mobile access prototyping
• W3C Geo-location API, ongoing
• In the Europeana Awareness project: native app
prototype with UGC-aspect
15. Aren’t you losing out in the app revolution?
• So why doesn’t Europeana focus on native apps?
• 1. We’re not good at it. We could learn the basics but
never become specialists
• 2. We don’t have the resources to cover Android, iOS,
and Windows
• To not lose out we offer instead an Open API
Letting developers and companies that are truly
specialist do what they do best
17. The Europeana API version 1.0
Version 1.0 launched in 2011
• Based on the OpenSearch standard
• Available to the Europeana network only
• About 20 implementations of the API in production
• And about 70 prototype API implementations
• Product marketing and Developer Outreach
• Simple website on Europeana Pro
• Simple documentation in Europeana Labs
• 5 Hackathons that were extremely successful
• We’ve learnt a lot. For example that developers love mobile!
21. The Europeana API version 2.0 (Q3 2012)
Is under development
• Simpler for developers (REST,JSON)
• More powerful (anything we can do, you can do)
• More scalable (logging, throttling, direct sign-up)
• Better documented (interactive docs, API console)
• Serves content in Europeana Data Model (EDM)
Is paired with a Development Outreach Programme
• Hack4Europe 2012 in May
• Copenhaguen, Warzaw, Leuven and perhaps more
• Part of the EU Digital Agenda
Will be an Open API
Made possible by the new Data Exchange Agreement
Mobile – trends, choices, plans The trends observed, the choices offered to us, the path Europeana is on This presentation is CC-BY-SA, http://creativecommons.org/licenses/by-sa/3.0/ I’ll do a quick intro of myself and Europeana here as well, the 1-minute summary
I won’t display the general numbers of connected mobile devices overtaking PC-devices etc. Those numbers you can find on the web. Or just observe all around you. Note – this isn’t really specific to Europeana or GLAMs but a global trend with liocal variations
Culture on the Go http://www.europeanaconnect.eu/documents/D3.1.3_Annex_Culture_on_the_go.pdf An analysis on mobile usage of Europeana based on 1 year of usage logs Ca. 70% iPhone users, then Android and far behind the others (Blackberry, Windows, Symbian) With numbers related to the projected growth of mobile Europeana users Dec 2011: 6% Dec 2012: 16%
Culture on the Go An analysis on mobile usage of Europeana based on 1 year of usage logs Ca. 70% iPhone users, then Android and far behind the others (Blackberry, Windows, Symbian) With numbers related to the projected growth of mobile Europeana users Dec 2011: 6% Dec 2012: 16%
Jakob Nielsen’s quick summary at www.useit.com/alertbox/mobile-sites-apps.html
Native apps advantages/disadvantages
Web advantages/disadvantages
Europeana’s decisions regarding “mobile choices”
Where we are now A portal that is decent on tablet A portal with a mobile specific stylesheet Exhibitions that are decent on tablet Exhibitions that don’t work well on mobile
These are the default stances Europeana takes as we re-design and design web sites Mobile first is a design philosophy that focuses on mobile first progressively enhancing the site at increased screen-sizes. Responsive design is a design technique that presents the pages content as effectively as possible at varying screen sizes
Our plans as they look now
Responsive exhibitions, prototype screenshots Taken in Screenfly, http:// quirktools.com/screenfly / iPad in portrait mode and iPhone in portrait mode Using Isotope JavaScript
Europeana Connect Rich Mobile Client prototype Pure web application It looks like an iPhone app but it isn’t! Uses the W3C Geo-location API to access GPS-data Which we will try to apply to both our portal and for exhibitions with a geo-component
Europeana Connect Rich Mobile Client prototype Pure web application It looks like an iPhone app but it isn’t! Uses the W3C Geo-location API to access GPS-data Which we will try to apply to both our portal and for exhibitions with a geo-component
Our plans as they look now
So why don’t we focus on apps? 1. We’re not good at it 2. We don’t have the resources to cover all the Oss So you’re losing out on the app revolution!? No, we don’t think so because we’re armed with an API!!!
For more info on our API-offering visit: http:// pro.europeana.eu /web/guest/re-use-data
Inclusion: Casual Curator Android application for curating and sharing personal collections of Europeana content Mashup with Freebase User selects up to twenty images forming a gallery Giving it a name User publishes/shares gallery on social networks
Commercial potential: Art4Europe Android application identifying artworks Uses image recognition Or QR-codes Uses Google Translate to translate descriptions of the artworks Can also read the descriptions through speech synthesis Can be built and deployed per museum/institution Can then be marketed as a free app or for a fee Or freemium Can also include links between artworks and the museum shop to by replicas, posters or other on demand services
Innovation: Time Mash An Android application Search and Geo-location aware search of Europeana Google maps Allows users to take photos and connect with Europeana objects Allowing for Then – Now photo comparisons User photos uploaded to Blogspot or Flickr Includes geotags through the users current GPS position
Yes, we’re eating our own dog-food… This together lays the foundation for a business model where Europeana focuses on core businesses like quality metadata and an open API thus facilitating innovation and R&D outside of Europeana proper Launches in Q3
So the idea is that WE dion’t try to build those fantastic mobile apps. What would YOU like to build!?
Thanks! Just google me an you’ll find me on Twitter, LinkedIn, Google+ inter alia