Specific notes from prototype, audit, workshop, and critique work — not star ratings.
We arrived with a 90-event wish list. The studio cut it to a journey map we could actually defend. Two weeks later engineering stopped asking what ‘screen_view_alt’ meant. I still wish we had booked the critique session earlier — we spent a week arguing names that paper would have settled in an afternoon.
The audit found three duplicate purchase events and a missing cancel path. Nothing flashy — just a cleaner catalog and a priority list our PM could schedule.
Half a day felt tight until the parking lot rule kicked in. We left with naming decisions written down, not another shared doc nobody owns.
Blunt notes on our onboarding analytics frames. Useful. Slightly bruising. We revised before showing investors.
Lesson completion path, education tablet
Yuna’s team needed clarity on which lesson interactions predicted weekly return visits. Network App Studio ran a three-week Interaction Analytics Prototype covering onboarding, lesson start, hint use, and completion. The delivered package included annotated mid-fidelity screens, an eight-event map, and a handoff brief for their analytics engineer. After internal usability sessions using the prototype as a discussion guide, the team postponed two vanity events and prioritized hint-use properties that research could interpret without a custom dashboard.
Remote sessions from Namhae worked better than expected. The printed-screen photos they sent after each workshop kept our Seoul office aligned.
We use essential cookies to run the site and optional analytics cookies to understand visits.
Read the details on our cookies page.