In order to create the workflow that is easy to extend and also to access the baseGameManager class was created. All other game managers extending the base class. That allows to be sure that the game state will always have needed data fields.

Main technical goal of the spin-game is to detect when player has made a full rotation with the circle. Visually player rotates the sphere completely however in code we only check for the 4 points around the sphere. By reaching each of them ones you reach small goal and sphere gets smaller.

It is worth mentioning that originally there was no visual rotation and it was really hard for the player to determine if the turn happens.

Path minigame was solved by creating a class representing for each path and then assigning methods from the manager class to path image callback. After starting to drag a tile along the path by either stop clicking or moving tile out of the path you will trigger this objects Input out callbacks. This allows to create a simple solution for tracking if tile is moving along the path or not, without explicit and complicated path checks.

Main challenge in tap mini-game was creating a possibility to track the order in which tiles were pressed. When player taps out or taps the tiles not in the order they have appeared on the screen his combo should broken. Each spawned tile is stored in the array, when we click on the tile we can check its current index and if its 0 we increase combo and remove this element from the array. In case index is not 0 we break combo and still remove the element. This way we can easily keep the order of elements and allow for the player to recover by pressing rest of the tiles in the correct order.

Additionally there are two types of the tapping games. By creating the main TapFigManager we can inherit its functionality and modify in StackFightManager. We reduce the code repetition and also it makes further updates easier.