Michael Details
Michael is building a travel app that aims to digitise travel guidebooks that people use to find interesting cultural attractions across South East Asia. The idea is that the app will have a map that will show where users are currently, and provide the best way to get to attractions around them. Once they are at the attractions, the app will also show users pre-created content that explains what they are seeing and the history. He want to build individual apps for different countries, starting with Thailand. Once Thailand has launched and shown success, he will roll out the same model across other countries.
Features (taken directly from an email he sent me):
1. Arriving in the greater location function. Once the user arrives in the greater location, we should offer comprehensive and expandable street maps. We not only provide the map, but we pinpoint the user therein in relation to his journey and we also pin thereon all recommended locations which we then detail. The first greater locations in Thailand will be Bangkok, Ayutthaya, Chiang Mai, and Phuket.
The suggested third-party plugin maps are Google, and LocationIQ. (www.locationiq.com). We need to review these options for technical and maintenance costs issues. Maybe you have other suggestions.
The software in the Prototype for this function will be the same for each greater location map so I would like to replicate this location function in the Prototype for the above mentioned four countries to create the greater potential for content in the minds of the parties considering the prototype.
- IIlustrating movement within the greater location (routing).
As the user moves the user needs to understand where he is and accordingly where his movements should be to get to the recommended locations. Again, this can be a plugin.(https://www.locationiq.com/routing)
The routing function should be illustrated in one greater location, say Bangkok for the Prototype. For the App we should include a duplicate of the software on the greater location maps sourced as above.
3.Pinpointing all recommended specific locations.
This is the geofencing and several third-party plugins have been discussed. The App should include in the Content Management System facilities for me or staff to insert in the GPS settings after an on-location check and audit. Third party software (Proximi) provide a platform to do this which is independent of our Content Management System. A self-owned GPS set up is preferred. Maybe cost estimates for both a plug in, and a self-owned system should be provided.
4. Pinpointing sub-locations within specific locations, such as fortifications, museums, and temples.
Here we note the crowding issue and need to decide upon high density systems such as Proximi or use image recognition. A costing for each system should be offered.
I will provide all maps or diagrams of these sub-locations. We need to consider routing options for some of the sub-locations.
The Content Provision Functions.
- All content will be stored in the Database managed by the Content Management System(CMS). I presume this is the same as a web site management system. It should be such that no programming support is needed to upload and remove content and even create new country or language version Apps.
2. The storage capacity should be for millions of English words and some tens of thousands of images. Foreign language fonts hopefully may be needed later.
3.The index system for Content should provide at least five levels of sub sections, are more available?
Each sub level should be capable of indefinite number of subtopics. For example, detailing each item within a subcategory in a museum or temple.
4.In my web site system I can automatically create a duplicate CMS channel for Content to attach to a new web site and this function is needed to attach to future country apps within the total App structure, so that programming is not needed (or minimal at least).
5.Whilst there is one master App (Asia’s World App) there will be separate Apps for each country. This is needed for subscriptions, B2B requirements, for different launch dates for new countries, access to different language versions, simplifying user vision, etc.
6.The CMS should have a tiered authority login system with the Editor having full authority to approve deletions and additions of Content and persons authorised to operate the CMS.
7.The CMS should enable internal and third party back-links insertions into content pages.
8.All App pages should have a URL system or something similar.
9.The Database and CMS should be capable of being stored on any commercial server provider.
10.The Database and CMS software should be license free and accessible to industry service support.
11.The Database and CMS software should provide a selection of agreed App page formats, which can be selected any time by the Editorial Team.
12.The Database and CMS software should enable The Editorial Team to back-link and insert web site pages from Asia’s World related web sites.
13.The Database and CMS software should be structured to enable or remove affiliate marketing and industry advertising back-links.
Data Accumulation
I welcome your advice as to what data accumulations software and storage capacity you provide as standard.