TicketCo Experience / Original published motion study
01 / TicketCo Experience
The context
A published motion presentation of TicketCo’s SaaS event experience. Explore the platform redesign case study for the Figma system, responsive web and native product-design work behind the screens.
Reading the problem / TicketCo Experience
The workspace has a rhythm, but the task still leads.
This film communicates a selected TicketCo experience. It is a presentation of the product rather than the complete core-library story.
This published SaaS film communicates a selected TicketCo experience; detailed operational and core-library decisions belong to the linked product case studies.
How can interface motion make a dense SaaS experience easier to follow?
Evidence: the project account and the attributed artifacts on this page. Process drawings and interaction studies are reconstructed explanations; numerical research or business results are included only where separately supported.
02 / TicketCo Experience
The design focus
- SaaS interface presentation
- Visual hierarchy and flow
- Product design connected to communication
The process / TicketCo Experience
A direction.
A way to build it.
The SaaS film follows an interface beat rather than attempting to replace the detailed operational case study.
A schematic of sequence and overlap, not a dated project schedule.
Choose the event context
Establish the information that makes the workspace meaningful to a viewer.
Define the interaction beat
Select the change the film needs to explain and where reading time is necessary.
Explore interface motion
Connect the approved SaaS scenes through transitions that preserve hierarchy.
Review the product summary
Resolve the sequence without turning the presentation into a business-results claim.
How can interface motion make a dense SaaS experience easier to follow?
A SaaS motion study needs enough event context for interface movement to make sense. The workspace can then unfold through a selected interaction before the sequence resolves. This presentation focuses on communicating the experience, while the linked system case study explains the underlying component work.
Journey map / TicketCo Experience
See the whole task in context.
Choose a step to connect the person’s intent with the interface and the design decision.
Current intent
Set the event context
This published SaaS film communicates a selected TicketCo experience; detailed operational and core-library decisions belong to the linked product case studies.
- Interface context
- Event context
- Review question
- Which legacy actions must remain directly accessible to experienced organizers?
Representative task sequence and recovery path, not a measured emotional curve or historical research map.
Behind the experience
From composition to a consistent deliverable.
For TicketCo Experience, this map connects “Set the event context” to “Summarize the experience”. Read across to follow the task, then select a layer to inspect the interface, design and delivery references behind it.
| Layer | Set the event context | Reveal the workspace | Follow the interaction | Summarize the experience |
|---|---|---|---|---|
| The task | Set the event context | Reveal the workspace | Follow the interaction | Summarize the experience |
| Visible interface | Event context | Event context | Workspace sequence | Product summary |
| Design checkpoint | This published SaaS film communicates a selected TicketCo experience; detailed operational and core-library decisions belong to the linked product case studies. | Establish the event context that gives the workspace meaning. | Follow one interface change long enough to understand it. | Summarize the product experience without claiming a business metric. |
| Implementation reference | Establish the information that makes the workspace meaningful to a viewer. | Select the change the film needs to explain and where reading time is necessary. | Connect the approved SaaS scenes through transitions that preserve hierarchy. | Resolve the sequence without turning the presentation into a business-results claim. |
| Recovery | Incomplete configuration → explain the missing field → return to the action | |||
A reconstructed delivery map: the implementation row summarizes design-process dependencies, rather than claiming to document the original backend architecture.
Guide attention through the workspace.
Reconstructed comparison of design approaches. These are review studies, not a claim that both directions were historically tested or shipped.
What this direction changes
Guide attention through the workspace
Uses timing and composition to establish the next meaningful interaction.
Build the film around a legible interaction beat.
The reconstructed storyboard moves from event context to workspace and product summary. It asks where the viewer needs time to read and where a transition can carry them forward. Showing more interface detail is useful only when its relationship remains understandable.
01 / Event context
TicketCo ExperienceSet the event context
OpeningResolve
Reveal the workspace
Establish the event context that gives the workspace meaning.
02 / Workspace sequence
TicketCo ExperienceFollow the interaction
OpeningResolve
Follow the interaction
Follow one interface change long enough to understand it.
03 / Product summary
TicketCo ExperienceSummarize the experience
OpeningResolve
Summarize the experience
Summarize the product experience without claiming a business metric.
Try the interaction
TicketCo Experience / Composition study
TicketCo Experience01 / 03
View 01
Event context
Establish the event context that gives the workspace meaning.
TicketCo ExperienceSet the event context✳
Starting context
Set the event context
Interface motion must respect the reading hierarchy.
Retain the distinction between event headings, interface labels and supporting data while the workspace moves. The film needs a reading hierarchy as well as a visual rhythm.
Documented families / Public SansTicketCo Experience
Set the event context.
Summarize the experience.
HeadingWorkspace sequence
24 / 30 px · regularBodyHow can interface motion make a dense SaaS experience easier to follow?
16 / 26 px · regularLabelSummarize the experience
12 / 18 px · regularStateIncomplete configuration → explain the missing field → return to the action
12 / 18 px · regularPublic Sans is verified in the original Figma typography board; these role samples use an illustrative scale.
TicketCo core library on Figma ↗Verified in the project’s source library
Foundations become reusable interface behavior.
- AtomsColors, typography and shadows
- MoleculesControls, selection, validation and chart families
- OrganismsLarger dashboard, data and checkout compositions
- TemplatesA separate level for reusable page structure
- PagesAdmin Sales and Ticket Buyer, both marked Ready for dev
Source library inventory / Refer to the linked catalog or design file for original variants and usage.
- Buttons
- Text field
- Select
- Stepper
- Alert
- RadioButton
- Checkbox
- DatePicker
- Chart/Line
- Chart/Bar
- DATA GRID
- DASHBOARD HEADER
- DASHBOARD NAV
- INVOICE LIST
- CHECKOUT CART
Choose clarity over the number of screens shown.
Which legacy actions must remain directly accessible to experienced organizers?
An event-management workspace needs an anchor before its panels begin moving. Establishing that context gives later changes an understandable relationship to the task.
Which patterns can web and native experiences share, and where should platform behavior differ?
The film should communicate a selected experience rather than imitate a complete training walkthrough. The product-design account is the place for deeper workflow and system detail.
Retain the link between screen and story.
The original SaaS presentation is part of the broader TicketCo portfolio. A production handoff needs the approved interface scenes, the intended focus of each beat and the transitions that connect them, without replacing the interface’s own hierarchy with unrelated motion emphasis.
A future AI-assisted adaptation should work from the existing film and current product references. Review whether the new cut still makes the event context and interaction readable before adjusting pacing or promotional copy.
The motion study communicates the SaaS experience; the separate TicketCo system case documents the broader redesign contribution.
Accessibility & standards
Access belongs in the design.
For this ticketing experience, prioritize seat-selection alternatives, availability announcements, reservation time limits and recovery without losing a selection.
WCAG 2.2 AA · EN 301 549 · APCA · WAI-ARIA · Platform guidance
Turn the palette into usable roles
Document approved text/background combinations for body text, large text and UI components. Assess functional content against WCAG 2.2 AA; use APCA to refine type size and weight.
Carry identity without losing meaning
Provide non-color cues, readable type hierarchy and accessible template reading order. Review captions and a reduced-motion alternative for product films and animated applications.
Make the rules usable in production
Include accessible color tokens, component states and content guidance in designer, developer and Claude/Codex references. Logo presentation alone does not establish interface accessibility.
Review scope & standards references
These are design references and review priorities, not a claim that this historical project passed a WCAG audit. Record criterion-level evidence, assistive-technology and device results, unresolved issues and retest outcomes before making a conformance statement.
APCA supplements the WCAG 2.2 contrast checks; it does not replace them. WCAG 3 remains a draft. EN 301 549 v4.1.1 is the latest published edition checked on 6 November 2026; its publication and its formal EU legal citation are separate matters. Confirm the applicable procurement or legal baseline with the client.
Outcomes & scope
What the work delivers.
- Original published motion study. The linked design-system case study describes my broader project contribution.
Results are described within the documented project scope. Illustrative studies are identified separately from original project artifacts.
Review & next iteration
What needs to hold up in use.
Use these questions to review TicketCo Experience against the behavior the design is intended to support.
- 01
Can the viewer identify the selected event as the workspace changes?
- 02
Does motion preserve the hierarchy of interface labels?
Project-specific acceptance questions for a future review, not reported usability-test results.
Reflection / TicketCo Experience
What I’d carry forward.
Moving interface panels should help a viewer follow the workspace. Pacing is successful when it clarifies the product rather than competing with the task on screen.