File fewer tickets. Ship events in two minutes.
Aiko is a game designer on a mobile F2P with 300K MAU. Every drop-rate tweak is a three-day engineering request. Every season is a JIRA thread. Here's the week she takes the timeline back.
Mobile F2P game designer at 300K MAU shipping live ops events without engineering tickets.
The offer that took two weeks
Aiko wanted a 48-hour double-XP offer for the top cohort. It took two weeks in the old stack: design doc, engineer pickup, config push, QA, staged rollout, monitoring. By the time it shipped the window had closed.
She opens Canvas on a sample project and drops a Seasons event onto the timeline. Scope: top-cohort segment, 48-hour window, XP multiplier 2×. The preview dashboard confirms which players are included.
Economy tuning
She adjusts drop rates for the seasonal chest — wires a reward curve node to the season's config. Canvas shows the before/after distribution side by side. Saves as a draft, shares the link with her PM for sign-off.
A/B against next month's cohort
The PM wants to test the new drop rate against the current baseline. Aiko adds an A/B split on the same Canvas, holds out 10% of the segment, and wires both arms into the Lens dashboard. No JIRA ticket.
Ship and watch
She schedules the event for Thursday 18:00 local per region. Season launches on time, no deploy, no on-call engineer. Lens tracks arm performance live; the A arm is +4% on session length by Friday morning.
Roll the winner to 100%
Aiko promotes the winning arm to the full segment with one click. The losing arm archives. The engineering team, who were busy with an actual feature, didn't hear about the experiment until standup.
“I stopped asking permission to ship events. It changed what I can do in a quarter.”
Your live-ops calendar, on the canvas.
Bring your seasonal calendar. We'll show you the same week, shipped in an hour.