June’s Journey

System Design:

Creation of a ‚Game Systems Map‘
Creation of a ‚Compulsion loop tool‘, allowing to easily see connections between features, motivations, time scales, as well as being a screenshot library

Feature Design:

Dedicated Feature Designer for extending ‚Memoirs‘ (=albums), June’s Journey’s most important feature:

‚Encore‘ feature (Replay an older album after finishing the current one)
Star Flashbacks
Album Experience improvements (f. e. defined improvements for the new pack open animations, and other upcoming improvements)
‚Charms Quest‘ feature
More upcoming features

Economy Design:

Dedicated Economy Designer for D2C:

Balancing of a massive upcoming feature, impacting many other parts of the game
Several smaller balancing requests (Android welcome gift, ‚Celebrations‘ event,…)

Android: https://play.google.com/store/apps/details?id=net.wooga.junes_journey_hidden_object_mystery_game
iOS: https://apps.apple.com/de/app/junes-journey-hidden-objects/id1200391796

(Since May 2025)

Examples are most effective when they turn an abstract idea into a situation readers can inspect, compare, and remember. In education, a strong example does more than repeat a definition: it reveals how a principle works, where its limits lie, and which details matter. A well-designed test example in technical documentation shows the expected input, the resulting output, and the condition that connects them, making the underlying rule easier to verify. That structure is especially valuable in software guides, policy explanations, and scientific writing, where a small change in assumptions can produce a different outcome. Examples should also be varied rather than endlessly repeated, since contrasting cases expose exceptions and prevent readers from mistaking one convenient illustration for a universal rule. Clear labels, concise explanations, and realistic data further improve comprehension without turning the discussion into a catalogue of disconnected cases.