Backend Unity Game - Learner activity tracking
Budget: €12 – €18 EUR
Learner activity tracking
The task is to develop a backend to manage, track and store learner activity from a gamified language learning course – a learner/learning management system. This backend will communicate with the user’s frontend (a mobile app currently being developed) and it will store all relevant information.
Tasks
Database design and management
API for user management functionalities and user activity tracking functionalities
Ensuring upscaling and modularity
Programming languages: C# or Python
Data protection in motion and at rest (target users are children)
Detailed specs
For each learner:
User properties
Unique Anonymized ID
First language(s)
Second language(s)
Age range (not real age)
User tracking
Login/Logout times
Navigation sequences
What resources were visited
How much time was spent there
What was done:
Everything done OR
Everything “submitted” once resource is existed
For each activity in which learner does/learns something:
Activity ID and Field ID
Text produced (written or spoken, if available transcribed)
For each activity:
environment id: mini-game, dialogue or logbook
chapter id
activity id
The task is to develop a backend to manage, track and store learner activity from a gamified language learning course – a learner/learning management system. This backend will communicate with the user’s frontend (a mobile app currently being developed) and it will store all relevant information.
Tasks
Database design and management
API for user management functionalities and user activity tracking functionalities
Ensuring upscaling and modularity
Programming languages: C# or Python
Data protection in motion and at rest (target users are children)
Detailed specs
For each learner:
User properties
Unique Anonymized ID
First language(s)
Second language(s)
Age range (not real age)
User tracking
Login/Logout times
Navigation sequences
What resources were visited
How much time was spent there
What was done:
Everything done OR
Everything “submitted” once resource is existed
For each activity in which learner does/learns something:
Activity ID and Field ID
Text produced (written or spoken, if available transcribed)
For each activity:
environment id: mini-game, dialogue or logbook
chapter id
activity id