Mobile Search: Context, Not Compromise
 

Mobile Search: Context, Not Compromise

on

  • 415 views

Each day, more and more smartphone users search for information while they're on the go. But many organisations today still don't have mobile search functionality on their site or even a mobile search ...

Each day, more and more smartphone users search for information while they're on the go. But many organisations today still don't have mobile search functionality on their site or even a mobile search strategy in place.

As a web professional, you already know the importance of mobile, and recognise that it presents a huge opportunity for you and your organisation. A great mobile search site will help your organisation by allowing your mobile site visitors easily complete what they intend to do, such as making a purchase or contacting you.

We are inviting you to join Gordon Grace, Funnelback Australia's Products and Services Manager, in this webinar where he will be exploring the concept of Mobile Search and answering questions like:

-What makes for a compelling mobile search experience?
-Do you need to 'dumb down' your content's discoverability for the small screen?
-How does search need to work differently in a tap-based, rather than typing-focused, paradigm?
and much more...

Statistics

Views

Total Views
415
Views on SlideShare
366
Embed Views
49

Actions

Likes
0
Downloads
3
Comments
0

1 Embed 49

http://www.scoop.it 49

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Mobile Search: Context, Not Compromise Mobile Search: Context, Not Compromise Presentation Transcript

    • Mobile Search: Context, Not Compromise Gordon Grace - Funnelback
    • Agenda• Compelling mobile search experiences• Mobile search user = second-class citizen?• Mobile as big-A accessibility• Dangers of hyper-localisation• Don’t make me think type
    • Not on the agenda Mobile Website v Native App v Responsive Design
    • Not on the agenda Tablet v Smartphone v Laptop v Desktop
    • Not on the agenda Android v iOS v Other
    • Making a compelling mobile search experienceDO’S AND DON’TS 6
    • Do• Make it fast / light / snappy• Make it work offline (as best as possible)• Progressively reveal complexity• Use <input type=“search”…>• Make yourself bookmarkable (if you’re a web app)• Let me scan
    • Don’t• Assume geo-location searching should persist in all contexts• Add clutter• Make unnecessary visits to the server• Force me to jump in and out of the desktop mode• Assume users have access to as many different devices / platforms as you do
    • Don’t• Break the back button• Make me wait• Make me type
    • Second-class online citizensMOBILE USER MYTH? 10
    • Arrogance and Inference of Intent• “Accessibility is just WCAG conformance”• “Users want a simple interface”• “Mobile users won’t want to see that content”• “Nearest is best”• “Road warriors will have their laptop, won’t they?”
    • Big-A Accessibility"But we are seeing increasing data aroundpeople simply not having the means to accessthe web other than a mobile device. You aresitting there with an iPad, but you cannot accessthe ATO or the Centrelink site in as effective away as I can on my laptop." Senator Ryan - Senate Estimates Committee (Finance and Deregulation) May 24th, 2012
    • Government StrategyWhole-of-government mobile strategyapproaching in 2012-2013 Australian Public Service Information and Communications Techonology Strategy 2012-2015 (Dept. Finance and Deregulation)
    • Let’s build something, already!NUTS AND BOLTS 14
    • UI/UX Considerations• Users scroll – why not scroll instead of paginate?• Query completion for mobile > consider using the ‘tap ahead’ design pattern.• Auto-correct after submission via query blending• Refine! If not by facets, then by context and/or sorting options.
    • Behind the scenes…• Separate profiles / contexts for mobile users (if only for analytics)• Same data source powering mobile web, responsive design and native app• Separate views, same data• Similar labels, results, features
    • Go all out• Make search central (hub/spoke model)• Pre-defined searches as views• Save searches as shortlists• User-tagged results• Filter cached copies for mobile viewing• Dedicated mobile front-end libraries (jQueryMobile, Sencha Touch, etc.)
    • Mobile.Enterprise. Search. 18
    • I want one!HOW MUCH? 19
    • Questions for your vendor• Speed: What’s the average response size and render time?• Coverage: How can responses be transferred across the mobile app / mobile web / responsive web versions?• Re-Use: To what extent can existing desktop- focused repositories, analytics and configurations be re-used?
    • Questions for your vendor• Functionality: What features from the desktop version of our app/site are being sacrificed for mobile?• Intel: How can I compare and contrast mobile users’ search behaviour?• Context: How will mobile users’ contexts be addressed?
    • Conclusion• Re-use, don’t re-invent• Respect your content• Respect your users