Button feedback without touching game rules
A button should respond visually to touch, but its small motion should not own purchasing or launching a game. I separated those responsibilities.

Our journey, behind the scenes, from idea to release.
Ideas, experiences and stories from the studio.
User InterfaceA button should respond visually to touch, but its small motion should not own purchasing or launching a game. I separated those responsibilities.
User InterfacePersistent Dalo preferences and CardGameAudioManager consumption, separating shared settings from their runtime effects.
User InterfaceDalo localization through JSON keys, per-language fonts, Persian letter joining and preserved numeric order.
User InterfaceDalo’s PopupController lifecycle: prefab versus scene ownership, closure cleanup and limits of automatic button wiring.
User InterfaceDalo menu tabs retain the latest pending destination, sequence exit and entrance, and restore authored RectTransforms.
User InterfaceDalo menu data from MainMenuPresenter to StaticMainMenuSceneConnector: entry costs, statistics and scene wiring.
Game ArchitectureDalo turn ownership: MoveNext versus assigning a leader, counter semantics and direction retained by Reset.
Game ArchitectureDalo’s Fisher–Yates shuffle, seed-based reproduction and the boundary between random ordering and game rules.
No articles found.