Domain modelling

[pklepa]

Description

We need to draft a general Domain modelling for the game design.

Ideally, the outcome of this story is to have a high level definition of all the game's entities and data flow drafted as a decision chart.

Data Reference

JSON object containing all the supported countries with:

• Country Code
• Country Name
• Flag image source
• Continent
• Related Country Codes (preset)

Game State

• Game Mode - Enum of:
  • Flag Count
  • Timer
• Progress
• Past Flags (to avoid repetition)
• Current Flag
• Current Options (?)

[pklepa]

@notstoe @gvituri, please take a look at the FigJam drawings containing the current definitions for:

• Project Entities
• Application Flowchart
• Business logic processes

For brevity, here's a couple of stills from the current domain modelling:

[notstoe]

Seems good, I think everything we need is there.

We should add a highscore local var that will be updated on game over? So when the app is closed, at least that will persist for now.

We'll probably use this library for that: mmkv

And for handling game state locally, we can use zustand? zustand

[gvituri]

Looks good to me!

Here are the changes I've included:

• Added Capital to Country Entity

  Added it with the '?' since it is not something we currently need, but something that could possibly come later as it's own game mode (gets a flag/country name, has to pick it's capital);

• Expanded App FlowChart to include post Game Over Options

  Nothing major, just a "play again" button leading to the game restarting and a "menu" button leading the player to the landing page

• Expanded App FlowChart to include Profile tab flow

  Simple in/out page with a single process of locally stored data retrieval and display and option to return to landing page