Considering that children from ages 4 to 7 have a greater capacity of learning new languages, Droplingo was developed with the purpose of teaching English for children in an interactive game.
Droplingo shows the child a few categories, and cards with familiar images. Their challenge is to relate, by dragging and dropping, the cards to the correct category, according to the images. When the child clicks on a card, the English pronunciation of the image name on the clicked card is played, and the spelling displayed on the back.
The child starts the level with a score of 100 points. For each correct move, 10 points are earned. For each wrong move, 10 points are lost. At the end of the level the child can register their score in a ranking, the top 10 are shown in the ranking list, in a classic arcade high score style (rank, name and score). The game also has a store, where the child's parents can buy them game benefits, among other things.
The first version of the game was evaluated by 4 teachers, 1 pedagogue, 1 speech therapist, 1 child psychologist, 4 parents and 5 children. Their feedback was essential to improve the project!
On this MVP the following releases have been made:
API responsible for managing the ranking, allows to add new players to the ranking and read the top 10 list
API responsible for managing the products sold in the store. Allows to create, read, update and delete products, but only the read action is actually performed in the game.
API responsible for approve, or not, the purchase transaction
API responsible for the frontend integration with all the apis. The game makes all the requests to the BFF, which is responsible for executing requests to the other APIs as needed.
You can read more about each API in their respective directories on the root of this repo.
You're currently on the Backend repository of this game, you may also want to execute the Frontend.
For the backend, you'll need to clone this repo
git clone https://github.com/jpgsaraceni/mvp-backendThen open each API directory and execute the instructions to get them up.
To contribute to this repository, you can fork it, create a new branch, make your changes, be sure that you've tested everything (preferably with automated tests) and then open a pull request.
Commit messages should begin with the type of the change followed by a short description of what you've done
- feat: a new feature
- fix: a bug fix
- docs: changes to documentation
- style: formatting, missing semi-colons, etc.; no code change
- refactor: refactoring production code
- test: adding tests, refactoring test; no production code change
- chore: updating build tasks, package manager configs, etc.; no production code change
We'll be happy if you follow the patterns above for your commit messages
We've already set a default pull request pattern, make sure to describe what changes you made, why you made them, what was happening and what you think should happen. Describe the tests you ran and which version of each tool/technology you used.