ERUNE
hybrid RPG board game and vocal companion · Arkada Studio
Erune pairs a physical dungeon crawler with a vocal mobile companion. its Spirit narrates quests, plays characters, reveals treasure and traps, and answers questions about rules and items. i contributed to Arkada Studio’s Flutter companion systems in 2025 as part of the development team.
THE WORK
01 · PROBLEM · APPROACH · OUTCOMEKeep the table in focus.
Erune supports solo, cooperative and versus play around a physical dungeon. the companion adds a narrator and characters, alongside answers about rules and items. the engineering problem is coordinating those interactions with the game unfolding on the board.
a choice, a spoken question and a playing sentence need different handling. the app has an interface; the design concern is keeping that interaction in service of physical play.
Coordinate voice and game state.
my 2025 Flutter work covered voice input, a sentence queue and text-to-speech for reading text aloud, alongside separate recorded character playback. music, effects and voice had distinct audio channels, with narrative choices and events connected to game flow.
the work also included game-service integration, campaign restoration, turns and map updates. saved game progress needed to remain connected to the current choice and the next part of the adventure.
A contribution to a shared game.
Arkada Studio lists Mohamed Elamin among Erune’s developers. that credit sits alongside the wider team’s writing, game design, illustration and music. the contribution described here is the 2025 companion engineering, not the whole game.
today, Erune’s companion is available on iOS and Android and requires the physical board-game box. the publisher describes a new app released in February 2026; the official imagery below shows that current product context.
At the table
02 · Board + appCompanion engineering and product context
03 · technical entries describe 2025 work; platforms, studio and genre describe the product.The game and companion
04 · current official product imagery, not a record of the 2025 implementation.Product specifications
05 · publisher-listed board-game facts and current app availability, not development outcomes.What the work taught me
06Separate interaction from playback.
player interaction and audio playback are different states. keeping them separate makes it easier to reason about when a spoken prompt ends and when the next choice becomes available.
Give each module a boundary.
audio, speech and narrative need explicit responsibilities. a sentence queue should coordinate with playback without taking over every sound, and voice input should remain distinct from the story it advances.
Keep language and voice distinct.
text language and voice playback are related, not interchangeable. treating text-to-speech and recorded character audio as separate responsibilities keeps language choices from becoming assumptions about which recordings are available.
Carry the campaign forward.
a choice changes more than the next sentence. campaign restoration, turn state and map updates need to stay connected so returning to saved progress has a coherent place in the adventure.
BUILDING A HYBRID GAME?
i work on Flutter companions that connect physical play with voice, audio and saved game progress. bring a hybrid-game project that needs those parts to work together, from spoken input to state integration.




