Skip to content

( Service 02 )

Digital Product

Web and product experiences with motion built in — so the interface and the movement are one file, not two vendors.

( Cadence )

8–14 weeks

( File )

Experience + motion

( Studio )

Toronto

( Team )

Product + motion

( Scope )

Screens, flows, motion

( Handoff )

A buildable file

( What we hold )

A product that hands motion to another studio will not feel like one house. We design the experience so the screens and the movement ship together.

02

(Digital Product)

© The experience

What the experience file holds.

Not a UI kit and a separate motion reel. Screens, flows, and the movement that belongs to them.

  • Product flows for the jobs the experience has to do
  • Screens for web and the product surface
  • Motion on the interactions that need it
  • Tokens shared by the still and the moving file
  • Prototype of the path, not only the hero
  • Handoff a front-end can build without a second read

03

(Cadence)

© 8–14 weeks

01 · Name

The job of the experience, the user, and the surfaces. A short brief is enough to start.

02 · Path

Flows and the screens on that path, including the states a launch film skips.

03 · Motion

Movement on the interactions that explain or confirm. The rest stays still.

04 · Handoff

One file for design and motion, with notes a build can follow.

04

(How it holds)

© Three rules

( 01 )

One file

Screens and motion are not two deliveries. If they disagree, the experience is not done.

( 02 )

Motion on the job

Movement explains, directs, or confirms. It does not decorate a static screen.

( 03 )

Web and product agree

The site and the product do not get separate visual languages.

05

(Questions)

© Digital Product

Flows, screens, interaction motion, shared tokens, and a prototype of the path.

Product design is the kit and the rules. Digital product is the experience — screens and motion — for a specific product surface.

Yes. The file is written so a build can take it without redrawing the system.

Send the product surface you want people to use.

A URL, a prototype, a backlog. We will tell you if an experience file is the next step — or if the product kit still has to come first.

Start a brief
Studio still for a digital product brief