Android Learning Game for small kids with Backend [High Production Quality]

Game development doc The school of games is an open source analytics platform that connects to all the other learning games and sends the data to the servers. The base “TSOG” game acts as a school or base game and opens the other games according to the curriculum that is downloaded from the server ( json config files ). Game requirements: Game should run on android ecosystem 4.4 or higher. Game should have high performance animations that are cute and playful for little kids. Game should have rich and colorful yet elegant colors for the game. Should use intents to open and share data with other apps. The game needs to have a welcoming music when it loads with the logo of the “TSOG” The pug should bark and invite the player in the game. Celebration music should be played on every success. Backend Requirements: The game should be able to work completely offline and should have a default config always loaded. Usage data should be sent from the other app to the main app to be sent to the server. If the game is offline, data should be collected locally and then sent to server when possible. A sample demo second app needs to be made to demo this functionality and data passing between base app and main app. How data can be passed between the two apps to be documented. The app backend should run on Google cloud and use google cloud storage. Code to be committed to github and made open source. User Flow: Login Login flow to register the user and keep him/her logged in till he/she logs out. Have one unique id per user used for tracking Doors to the school opens Avatar for the user gets loaded Classroom gets shown with the pug inside it 3 Windows new chapters The chapters shown are based on the config loaded from the server. Clicking on a window takes them to another child app. User plays in the other app Does any actions Usage data is collected On completion the main app is opened and usage data is sent. The main app opens Usage data is sent to server. The cycle from 5 continues. Development Phase 1: Define concept art for the app. Design user flows. Define server architecture to store all the data. Define data flow architecture between main app , other app and server. Phase 2: Create endpoints to pass data to the backend. Finalize game art and assets. Finalize music for the game. Phase 3: Game development. To be determined based on previous phases. Sample applications for inspiration: [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] A very early prototype of the game on web: [login to view URL] Our Mascot for game: Full document available on request.