This touring app s a map-centric application designed to assist visitors wishing to tour Seattle's art, food, music, and other cultural highlights. It utilizes crowd sourced data to provide comments, photos, links, and ratings for each stop on the tour.
The project was developed in four months by a three member herd of independent contractors that included 1 graphic designer and 2 software developers. Spatial Minds contributed application UI/UX design experience, application architecture, and both UI & backend implementation for all of the "geo" related functionality of the application, including:
- Flickable Map
- Tiled Map Server (TMS) back-end integration, cacheing, and optimization
- GPS Integration
- Point of Interest (POI) search
- POI storage
- Routing UI Design
- Routing back-end integration
The application opens to the "Tour Selection" page or the last screen used. The map is centered on the user's current location.
When a tour is selected, both the left pane and the map pane display the stops on the tour. The user can add, remove, or re-order any of the tour stops.
When a stop is selected in the left pane, the pushpin on the right pane is highlighted.
Selecting the i "information" button displays detailed information about the stop, including crowd sourced comments, photos, links, and ratings. Pressing the little man "directions" button computes a route from the user's current location to the tour stop, displays it on the map, and displays step-by-step directions in the left pane.
In addition to basic tour stop information and routing, the application includes a complete POI database search that allows the tourist to find a place for lunch or a quick cup of coffee. It includes directions on how to get there and how to return to the tour.
The architecture extended the existing Qt Mobility 1.2 design patterns by implementing custom geo-services and POI plugins. This approach allowed us to meet a VERY short timeline by using the Nokia OVI Maps back-end geo-services early in the project, and our custom geo-services plugins later on. By using the OVI Maps back-end early, we were able to keep developers busy implementing the front-end UI components. Later when the Service Broker based Geo-services were complete, we simply swapped in our custom plugin.