Application POI adjustments
Budget: $2,000 – $6,000 HKD
Overview:
The project is broken into the following:
1. A multi-platform mobile application for iOS and Android built using Unity.
3. A Content Management System used to update information within the application without further installations and application updates.
Problem: Mobile application loads various POI markers using a combination of in application and CMS data. Current solution requires that if a POI is added / removed from the CMS, a manual update to the mobile application code must also be made. In case of mismatch in number of POIs between frontend Application and CMS, the frontend Application crashes.
Goal:
Update the mobile Application to improve connect to new API endpoint provided by the CMS.
1. Remove hardcoded POI’s from the Application, instead a list of POI’s will be provided to the Application during its initial runtime update with the CMS, and POI’s will be generated from the provided response.
2. The XYZ placement of the POI is done in the application, requiring a tedious process of editing / building the project to determine accuracy of POI position. A NEW endpoint has been added to the CMS to determine XYZ data, and if the POI should be enabled or disabled. Changes to the application is needed to support this.
Objectives:
The source files for the Unity mobile Application will be provided for the following work.
[FRONTEND]
1. Handle mismatches between POI defined in CMS and frontend app.
1. Prevent app crash at any time.
2. Download and process POIs from CMS, including new properties.
1. Refactor existing code to support dynamic number of POIs
2. Refactor existing code to support dynamic GPS coordinates for each POI
Deliverables:
2. Modification to the Unity project sufficiently stable to be built on iOS and Android
The project is broken into the following:
1. A multi-platform mobile application for iOS and Android built using Unity.
3. A Content Management System used to update information within the application without further installations and application updates.
Problem: Mobile application loads various POI markers using a combination of in application and CMS data. Current solution requires that if a POI is added / removed from the CMS, a manual update to the mobile application code must also be made. In case of mismatch in number of POIs between frontend Application and CMS, the frontend Application crashes.
Goal:
Update the mobile Application to improve connect to new API endpoint provided by the CMS.
1. Remove hardcoded POI’s from the Application, instead a list of POI’s will be provided to the Application during its initial runtime update with the CMS, and POI’s will be generated from the provided response.
2. The XYZ placement of the POI is done in the application, requiring a tedious process of editing / building the project to determine accuracy of POI position. A NEW endpoint has been added to the CMS to determine XYZ data, and if the POI should be enabled or disabled. Changes to the application is needed to support this.
Objectives:
The source files for the Unity mobile Application will be provided for the following work.
[FRONTEND]
1. Handle mismatches between POI defined in CMS and frontend app.
1. Prevent app crash at any time.
2. Download and process POIs from CMS, including new properties.
1. Refactor existing code to support dynamic number of POIs
2. Refactor existing code to support dynamic GPS coordinates for each POI
Deliverables:
2. Modification to the Unity project sufficiently stable to be built on iOS and Android
Related categories:
Unity 3D