LottieFiles Digital Asset Management
Expanded LottieFiles Platform beyond animation into a workspace for managing and delivering multiple asset formats
- Responsibility
- Product design ownership
- Area
- Platform
- Product reach
- Creator and Plugins
Impact
Expanded the animation workflow to include images, SVGs, videos, and source files, giving teams one place to manage every asset.
- 6K+
- non-animation asset uploads per month
- +20%
- asset uploads in the month after launch
I led the UX, UI, and product workflows that expanded LottieFiles Platform to support images, SVGs, videos, and source files alongside animations. Early in the project, I built an AI-assisted proof of concept to make the core model and workflows tangible, helping stakeholders, product, and engineering align before moving into high-fidelity design.
Rather than creating a separate destination, I extended the existing asset model so these formats could use the organization, status, review, approval, versioning, and delivery workflows teams already knew. I also improved everyday asset management with multi-format and folder uploads, multi-file copy-and-paste, and drag-and-drop organization.
I defined the core Platform experience, guided how the model extended into the plugins, and designed the corresponding Lottie Creator experience, where I also contributed to front-end implementation.
Why it mattered
Customer requests and our own internal workflows highlighted a broader problem: related project assets were being managed across multiple services, making complete projects harder to organize, track, and deliver.
Key decision
Built on the existing asset model instead of creating a separate product area, preserving familiar workflows while adapting previews, metadata, and actions to the needs of each format.
Outcome
Teams adopted the experience to bring related project assets into one workspace, while stable CDN links and version control allowed deployed assets to be updated without redeploying products.

Kept animations, images, SVGs, videos, and source files together in familiar projects and folders

Created one upload flow for individual files, full folders, and mixed asset types

Made it faster to add several copied assets directly to the current folder
What scaled
The expanded asset model became shared infrastructure across Platform, Creator, and plugins, supporting consistent asset management and delivery across surfaces and later projects like Motion Systems.
Showing testimonial 1 of 2

