I’m Manvi Singh

← All work

Vision prototype · Perforce Jam 2026

An ecosystem for creatives, built into Blender.

▶ Watch the announcement 32 s
RoleSolo: concept, design, prototype
EventPerforce Jam 2026, 352 participants
ResultHonorable mention, Non-Coding Track; global finalist (top 25 of 145 ideas)
Built withClaude, VS Code, Blender
My prototype running inside Blender, sped up. The panel stays put while versions and experiments change the scene.

Creative teams lose time hopping between tools. I prototyped one panel inside Blender that brings planning, versions, experiments, collaboration and storage together.

Built on what P4 One taught me: protect creative work inside the artist’s own workflow.

A hackathon prototype, not a shipped product. The company plans to build the concept after further research.

The problem

Every switch breaks flow.

Plan, create, version, review, finalise: each step lives in a different tool. Teams collaborate on plans in P4 Plan, and review and comment on the work in P4 DAM. And creative work isn’t a straight line. Artists loop back and forth, so every loop is another switch.

C

Charles, a 3D artist on a racing game.He lives in Blender. His workflow doesn’t. An illustrative artist, not a real person.

PlanP4 PlanCreateBlenderVersionP4 One + P4 serverReviewP4 DAMFinalP4 serverExperimenttry ideas in betweenand back, again and again
every arrow is a switch to another tool

The idea

Bring the workflow to the creator.

Everything an artist needs, in one panel, without leaving Blender.

Perforce for Blender

PlanTasks and progress
VersionsHistory and branches
ExperimentsTry from any version
CollaborationShare and get feedback
Cloud storageSafe in the cloud

A continuous workflow, not a pipeline.

Creative work loops. Every stage happens inside Blender.

Plan→Create→Version→Review→Final
and back around again, all inside Blender

AI stays quiet.

Small helps, not a chatbot. AI suggests a name for each version or experiment and drafts its summary, and the artist edits before saving. A human stays in the loop, so they always know what they’re saving and how much storage it takes.

Planned, not built in the 48 hours

An illustration of the plan, using the sample project from my prototype.

48 hours

Iteration 1

First, the whole vision in Figma Make.

It was a 48-hour hackathon, with a lot happening in one panel. So I put everything together in Figma Make first, to see how it could all work without making the plugin heavy.

Iteration 1 in Figma Make, sped up. Sample project and names.
Iteration 2

Then I iterated.

The second pass put what matters most in front of the artist, and brought planning and review updates into the same panel.

Iteration 2 in Figma Make, sped up. Sample project and names.
The build

Then Blender pushed back.

Blender add-on panels are built from Blender’s own controls, so a lot of the rich UI I’d planned had to give way. The core made it: versions, experiments and the plan view, in Blender’s native UI.

The Figma Make panel, iteration 2: unsaved changes flagged at the top, a Create Version button, a rail of version thumbnails, the active version with Open and Share, and linked tasks
Planned in Figma Make
The plugin built in Blender: native collapsible sections, a Work and Plan switch, and a simple list of versions and experiments with Merge to Root, Open and Delete buttons
Built in Blender
What I had to cut
  • Rich UI. Much of the visual polish from Figma Make had to be simplified to fit Blender’s native controls.
  • The version tree. A collapsible tree of versions with their experiments inside didn’t work reliably, so I cut it for a simpler list.
  • Cover images. Blender could show them, but only very small, so I scaled them back.
  • Finishing. Polishing the plugin took the most time; many UI details didn’t behave as planned.

Where it fits

An ecosystem in waiting.

Powerful products, working as separate destinations. This is the connective tissue, not a replacement.

ProductRoleToday
P4 OneVersions and experimentsLive, evolving
P4 PlanPlanning and workLive, separate
P4 DAMReview and assetsLive, separate
P4Cloud storageLive, separate
Blender pluginEmbedded experimentsBuilt, planned for 2027
Unreal pluginEmbedded experimentsShipped, free on Fab

Why it matters

For creators

Fewer interruptions.

Plan, version and share without leaving the tool.

For the product

Connects P4 One, Plan and DAM into one experience.

Plugins become strategic, not peripheral.

For the business

Enables ecosystem bundling.

Differentiates Perforce in creative production.

What happened

Honorable mention.

Perforce Jam, May 2026, Non-Coding Track.

What’s next.

The company plans to build the concept after more research. What resonated most: the ecosystem thinking, bundling products and an easier flow for users.

What I built.

Solo: the concept, the flows, and a working prototype running live in Blender, made with Claude and VS Code.

The announcement

Anjali Arora announcing the Non-Coding Track winners at a Perforce global town hall. Captions transcribed from the recording.

More work

← Back to all workGet in touch →