Mobile Store Locator

Features and benefits

  • Five tips for your mobile locator

    A few of the lessons we have learned when designing and building store and stockist locators for the Mobile Internet. more

    top 5

  • Real time customer feedback

    Improve service levels by allowing customers to provide real time feedback on their experience at their nearest store.

    sml-feedback

  • Auto Locate – GPS

    Improve access to your stores by allowing your customers to find you using the GPS built into their smartphone handset.

    sml-auto-locate

  • Click to Call

    Make every opportunity count by ensuring customers are on the phone to their nearest store in a matter of seconds.

    sml-clicktocall

  • Content customisation.

    eHound ensures you maximise conversion by customising navigation, content and functionality for specific mobile devices.

    mobile-locator

  • Save money on producing Apps

    A store locator for the Mobile Web can save time and money on the development of apps for multiple platforms.

    sml-apps

The eHound Mobile Web Module has been designed to support location-based services across all mobile browsers, with navigation, content and functionality customised for specific handsets (eg iPhone), and categories of device (eg Webkit-enabled).

This Module offers a lower cost option when compared to the development of native application for multiple operating system platforms (iPhone, Android, Blackberry, etc).

Specific benefits include:

  • Automatic access to GPS where available
  • Resizing to portrait and landscape
  • AJAX and static maps automatically mapped to the device’s capability

The following classification is used.

  • High-End:

    These are modern large screen touchscreen/non-touchscreen phones with WebKit browsers. These browsers handle CSS and JavaScript very well, which means that most AJAX sites with native style components typically work great. Includes: iPhone and iPod Touch, Android, BlackBerry OS 6, Windows Phone, Palm WebOS.

    High-End Mobiles
  • Midrange:

    These devices can handle CSS reasonable well, so that iPhone- or Android-style interfaces generally look fine. Unfortunately, JavaScript support is poor. For these reasons, in most cases, the high-end site can be served up but maps need to be static. Includes: Symbian S60, 'High' BlackBerry Devices such as Blackberry Bold, Windows Mobile, Nokia E71, other Webkit-based devices.

    Midrange Mobiles
  • Low-End:

    All other Internet-enabled mobile devices. For these devices, we serve only the most basic styling and limited images.

    Low-End Mobiles