SundaySky · UX/UI Design Lead

Custom scene

From template to total freedom: start from blank.

Editor SaaS Core feature User testing Jan – June 2025
The studio with a blank custom scene open: a placeholder library popover offering Heading, Sub heading, Media, Button and Logo, and the scene lineup along the bottom.
35%Account adoption↑ from 20% in week 2
15.8%Visitor adoption↑ from 9.1% in week 2
19 of 23Users worked around templates with overlays

Pendo, first 90 days · FullStory, 23 sessions

Goal

Let marketers build their own scenes inside the platform, instead of hacking templates or leaving for other tools.

The challenge

Give them freedom without scenes that look or animate worse than our designed templates.

My role
UX/UI Design Lead
Team
PMs, Engineers, QA, Copywriters, CS
Tools
Figma, FullStory, Pendo, Jira
Timeline
Jan – June 2025
Process
Discovery → Design → Develop → Analyse
Presentation
A slide walkthrough
Link
SundaySky Help Center

Discovery

3 findings

01. Inspiration & benchmark

Users expect Canva-like editing: alignment, layering and asset libraries.

Not a competitor review: I looked at how six editors handle stacking elements, asset libraries, layering, hidden elements and alignment, to borrow patterns users already know.

  • Canva
  • Powtoon
  • Pitch
  • Synthesia
  • Biteable
  • Google Slides

Internal review · 6 editors

02. Behavioural observation · FullStory

Only 4 of 23 used overlays as intended. The rest hacked them into whole scenes.

Overlays were meant for text over media. Users bent them into custom scenes instead, and some duplicated scenes just to align elements. That behaviour, not a feature request, made the case for a real blank canvas.

Session recordings showing users stacking overlays to work around template limits.

FullStory analysis · 23 sessions

03. Scene actions · Pendo

The 3-dot menu was the main entry point, so its key actions moved onto the canvas.

Click data showed what users reached for most. Those actions left the menu for a new scene toolbar, which later hosted the placeholder popover.

The 3-dot scene menu open in the studio, beside a Pendo panel ranking all nine menu items by number of clicks. Counts obscured: client data.

Pendo click analysis · user interviews

Design

4 decisions

Main user flow

Four steps from empty canvas to a finished scene. Each one needed a decision.

  1. 01Add a custom scene
  2. 02Add a placeholder
  3. 03Position and scale
  4. 04Refine
  5. ✓Scene ready

Decision 01 · Add a custom scene

A sidebar button, as a compromise

How do we make it visible without restructuring the library or over-promoting a layout not built for animation? Product wanted it below the fold, a fair worry about quality. I pushed back: it hid what users came for. The sidebar button was our compromise.

Options explored
Four lo-fi options for the Custom scene entry point: flatten the grid, its own category up top, buried in the last category (Product’s ask), and a separate sidebar button (the compromise).

Decision 02 · Add a placeholder

A popover, not a left panel

A left library would match our other libraries, but placeholders only apply to custom scenes, so the panel would either vanish or sit disabled. A popover from the new scene toolbar appears only when it’s relevant.

Options explored
Three lo-fi options for the placeholder library: a left library on custom scenes only, a left library always shown but disabled, and a popover from the scene toolbar (selected).

Decision 03 · Position and scale

More canvas, less chrome

For the first time, canvas space mattered: users had to align, see guides and zoom. I cut every unnecessary gap: a shorter scene lineup, a shorter voice-over field and tighter margins.

Before → after
Before and after editor wireframes: the hatched space removed from the margins, voice-over field and scene lineup gives a larger canvas.

Decision 04 · Refine

A drag frame and dual-colour guides

Live rendering made dragging lag. Users drag a light frame that snaps to guides, and the scene renders once on drop. Guides are drawn in dark and light blue, so they stay visible on any media.

How it works
Storyboard: drag a light frame along the guides, then drop to render; legacy hidden-placeholder frames removed.

Design system

Built inside SundaySky's design system, extending it only where the feature demanded it.

  • Worked within SundaySky's design system (MUI).
  • Added new components: flexible placeholders.
  • Added a Popper / Popover component.
  • Updated components still using the old system.
Design system sheet: components, buttons, notifications, icons, labels, typography and colours.

Testing the concept · 4 studio users

What we learned, and what we changed.

Guides hard to seeDual-colour guides

Dragging felt slowDrag a frame, render on drop

Nobody pressed previewAssumption revised

Internal test · pre-release

Analyse

5 findings

01. Adoption · Pendo

Account adoption grew from 20% in week 2 to 35% by day 90.

Teams that tried it kept using it. Visitor adoption grew more slowly, so it spread within teams more than to each person.

AccountsVisitors
0%10%20%30%40%
Week 2
Month 3
35%15.8%
Day 90
CheckpointAccountsVisitors
Week 220.3%9.1%
Month 325.6%13.3%
Day 9035.0%15.8%

Pendo · exposure wasn’t uniform from day one, so the slope is approximate

02. Usage · Pendo

Creating a scene isn’t a stopping point: users go straight to adding placeholders, mostly media.

After creating a scene, users went to

45%Empty-state button13%Toolbar42%Other

“Open the placeholder library” events, not confirmed insertions.

Top placeholders added

Media45.9%
Sub heading20.5%
Heading19.4%
Logo10.3%
Footnote3.8%

Pendo path and placeholder events · last 90 days

03. Usability testing · Flexible Scene

A related feature, tested with 9 users, showed the same gaps.

  • Multi-select
  • Layer panel
  • Copy / paste between scenes
  • Guides hard to notice
  • Font size tied to the box

Fixed in phase 2

Usability testing · 3 internal + 6 external participants

04. What I’d measure today

Three of six goals weren’t tracked. Next time they ship with the feature.

RetentionAdopting accounts still active at 30 / 90 days

UsefulnessPublished videos with at least one custom scene

CompletionCustom scenes published vs. abandoned

05. What users told us

Used in most videos, often several per video.

Reported by a colleague about a year after launch: anecdotal, with no instrumented data behind it. Pendo feedback pointed to what came next:

“Need a way to align multiple items in space evenly.”
“Multi-select for bulk placeholder actions, like I can do in PowerPoint.”
No CTA button option, so the workaround was going back to a template.

Pendo feedback · anonymised

Lessons & next steps

The biggest lesson: user behaviour got this built. People hacking overlays into whole scenes was the argument, and it became an internal case for listening to users directly. Feedback then shaped phase 2: multi-select, layer management, bullet and CTA placeholders, and copy/paste between scenes.