Taletrack keeps moving fast and we are almost ready to start the development. There are still a couple of things to test first, there are stories to write, details to define, but we are getting there.
During this last week we have been working on the product specification, created diagrams and designed our first wireframes. I would like to share a brief product description here and ask you for your feedback on it:
Taletrack is a digital platform for distributing gamified adventures with the objective of converting visits to local, historical and cultural sites into unforgettable and memorable experiences. Taletrack takes video gaming out on the streets and helps its users to better memorise what they’ve seen and learned about a place or a fact.
The full Taletrack Digital Platform consists of three parts:
1. Discovery App: iOS or Android Discovery App on which users can select and play an adventure of their interest.
2. Curator Panel – web-based Curator Panel for creating and editing adventures.
3. Curator App – iOS or Android Curator App for creating and editing adventures on the go.
The Discovery App flow and functionality will be the following:
The user downloads and opens the Taletrack app. He then chooses an adventure based on his current location and interest. Adventures are displayed in a list view or map view ordered by distance from the users current position. Adventures can also be searched on the list view by specifying a location name, author or keywords from the adventure title and/or description.
Tapping an adventure, an additional view displays its details including title, description, author and images. We will add video and audio in the future.
To start an adventure the user needs to register or login by specifying username, email, name and age and login. Name and age are necessary for legal purposes.
Adventures consist of a number of points of interest (POIs) and missions.
POIs are locations identified by an ID and their coordinates and can have additional information attached. A POI can be a cultural site, a local business or any other point on a map, that is needed for the flow of an adventure. POIs usually have a title, a description and additional information in form of image, video or audio.
Missions are tasks the user has to accomplish during the flow of an adventure. These missions can be as simple as “go to POI X” and make the user follow a route. Missions can also require a user to check-in at a place, take a photo, answer some question, … etc.
A mission usually triggers the next mission and creates a sequence, but some might also be activated in parallel. Missions can be active/in-active, completed and hidden. Other mission states might be added in the future. They are displayed in a missions view and can be viewed throughout the aventure.
Does that make sense? Is it understandable? I would be great to get your feedback.
Here are also some of our first wireframes.
As always, I appreciate very much your time and feedback and hope you like what we are working on.