Haggle

1
Haggle

• Lynne Hall, Marc Hall,
• University of Sunderland

2
Overview

• Who are the likely users of Haggle?
• Design context
• Making Haggle input as minimal as possible
• Using display to support choice
• 4 Profiles are these the right users?
• Design Considerations

3
The Users of Haggle

• Away from home requiring accommodation
• Recreation
• Business
• Adventurous
• No booked accommodation
• Unlikely to use Haggle
• Family groups particularly with children under
  10s
• People with special requirements
• 70

4
Design Context

• Haggles aim is to get repeat users
• Consideration has to be given to both casual and
  frequent users
• Casual 1st use must require minimal information
  primary fields see further slide
• Frequent based on profiles
• Haggles competitors

Start page for hotel bookings
5
What do they ask?
6
Designing the Basic Haggle

• Input
• Admin fields (e.g. arrival, departure, etc.) must
  be fast, easy, not requiring any effort or
  thought (most travellers tired or in a hurry when
  arriving to a new location)
• Hotel location
• The user will have a specific place they wish to
  be near (even if it is here)
• Fields used for all 4 application designs (based
  on 4 distinct user profiles)

7
Haggle Primary Fields all the user needs to
enter to begin the search

• Destination
• Default to nearest likely location (e.g. if in
  northern Spain Barcelona)
• Must be changeable to any areas of product
  coverage perhaps as drop down?
• Hotel location
• Default to where they are as near as possible to
  here
• Range of options postcode / near airport / city
  centre dont mind
• Arrival date
• Default to today
• Departure date
• Default to tmrw
• Ideally should also be modifiable and displayed
  as number of nights
• Number of rooms
• Default to 1
• Number of people
• Should ignore children field as users of Haggle
  unlikely to be with children (discussed with
  focus group of parents who would otherwise fit
  into one of the Haggle categories)

8
Haggle Input Screen

• Only display Haggle primary fields
• No need to put in secondary considerations
• These can be provided by display screen

9
Haggle Input Screen

• Paper prototype (photo to add)

10
Displaying results

• Most important part for the user
• Must be possible to display by multiple and
  combinations of options
• Price (both directions)
• In terms of facilities
• Nearness to preferred location
• Best bargains
• Star ratings
• Perhaps ask what the display should be between
  the request and the results (keep user occupied)?

11
Haggle User Groups

• Backpacker
• Affluent Gappie
• Spontaneous Weekender
• Dynamic Business Traveller

12
Backpacker Characteristics

• Predominantly young
• 18-19 gap year school -gt university
• University students or recent graduates
• Price of high importance backpackers typically
  limited funds
• Willing to take low cost accommodation (e.g.
  hostels)
• Willing to take rooms with limited facilities
  (e.g. no en suite)
• Requirement for technical infrastructure (e.g.
  Wi-fi / internet)
• Choice may be impacted by social opportunities
  (e.g. hotel aimed at backpackers / young people
  travelling)
• Backpackers often travel in groups
• Length of stay may be of a wide range

13
Backpacker Facility Profile

• Wi-fi / internet
• Kitchens / self catering
• Restaurant / Café / Bar
• Visited by other backpackers
• En suite
• Near public transport

14
Affluent Gappie Characteristics

• 30 professionals taking a career / lifestyle
  break
• Interested in value and bargains
• Standard quality hotels (e.g. en suite)
• Quality restaurant facilities / access
  Requirement for technical infrastructure (e.g.
  Wi-fi / internet)
• Likely to have specific location requirements in
  relation to city highlights

15
Affluent Gappie Facility Profile

• Wi-fi / internet
• Restaurant / Café / Bar
• Near to specific locations
• Near public transport
• Fitness Facilities
• Pool
• Spa
• Air Conditioning
• Laundry / Dry Cleaning

16
Spontaneous Weekender Characteristics

• Young professional around 25 to 35
• May be looking for party city experience
• Last minute decision to take a break from
  stresses of work / family
• Interested in value and bargains
• Good quality hotels (e.g. en suite, spa, pool,
  gym, reception with booking and organising
  facilities)
• Restaurant facilities / access room service
• Likely to have specific location requirements in
  relation to city social activities
• Nearness to public transport / taxi ranks
  important
• Likely to be travelling by air

17
Spontaneous Weekender Facility Profile

• Airport Shuttle
• Restaurant / Café / Bar
• Near to specific locations
• Near public transport
• Fitness Facilities
• Pool
• Spa
• Air Conditioning

18
Dynamic Business Traveller Characteristics

• Age 21-55
• May need to be near intended meeting location
• Internet / Wi-fi also may have requirements for
  additional business services
• Possibly looking for pool gym
• Restaurant facilities / access room service
• May need airport shuttle
• May arrive late and leave early flexible check
  in / check out facilities
• Price may be key factor
• May require parking

19
Dynamic Business Traveller Facility Profile

• Internet / Wi-fi
• Air conditioning
• Business Services
• Laundry / Dry cleaning
• Airport Shuttle
• Restaurant / Café / Bar
• Fitness Facilities
• Pool
• Parking

20
Basic Haggle Output screen

• Sort results by Dropdown
• Paper prototype to add

21
Design Considerations

• Providing directions from here to there including
  by public transport
• Profiles
• Provide the four suggested and let user modify
• Look and feel
• Is it worth customising it for the different
  possible user groups?
• Extended information for user with time on their
  hands which make use of browser capabilities and
  available on web and device and provide more
  information about hotels and locations