Morkahja — Visual and Interaction Design
Player experience
Morkahja combines an illustrated fantasy encounter game with a persistent character dashboard. The original development journal records the May 2026 shift from a first playable browser checkpoint to a layered interface: avatar selection, encounter art, four solution slots, dice outcomes, rewards, a radial navigation menu and game-state overlays.
The visual language is not merely decoration. Encounter transitions deliberately pace discovery: the May 21 journal records a 720 ms encounter crossfade and 1100 ms solution/dice reveal. Reward icons animate toward footer targets and losses are visualized against avatar and outcome slots. These choices communicate consequence and progress.
Dashboard and social surfaces
The journal documents SCRIBES as an in-world event feed, achievement panels and attention indicators, friends and avatar summaries, an expansion browser, settings and About Us credits. The About Us area must credit Babuni.dev as author and preserve distinct credits for contributors such as music composer Nikita Malko.
Accessibility and verification boundaries
Source presence does not prove successful operation on current mobile devices or with assistive technology. Keyboard/focus flows, reduced motion, readable contrast, touch layouts and outcome readability require their own tests. The journal's past recorded observations should not be relabeled as new results from this documentation audit.
Portfolio presentation
The design story should show dated evolution: first playable checkpoint (May 18), music and event pipeline (May 19–20), expanded encounter-result motion and achievement surfaces (May 21–22), and deployment/social polishing (May 23 onward). Distinguish original assets and author-approved art from AI mockups or source-only components. Preserve screenshots and evidence where permission exists; do not infer an approved final visual identity from the code alone.
See original chronological journal, development-history guide, and content inventory.
Document information
Author: Babuni.dev
Evidence: Existing repository journal and client structure; historical report, not new visual acceptance testing.