ishandeveloper

Yes! That's actually one of our favorite use cases. Check out the SF Vlog example project at demo.usecardboard.com, it covers exactly this!

Thanks so much, glad it worked well!

There is an undo button — it's on the bottom right of each user message in the chat. That said, sounds like it wasn't obvious enough, so I'll rethink the UX there for sure!

- On Remotion, yeah, not sure it's the right fit, but honestly the sheer capability of models at writing code these days has surprised me. Funnily enough, this is how I used to make small graphics for videos 2-3 years back when I knew nothing about After Effects.

We've been eager to experiment with this for a while, just have to prioritize other user requests for now. Will definitely try a few approaches and see what sticks. (Also noticed they have an experimental client-side rendering version built on mediabunny, haven't tried it yet: https://www.remotion.dev/docs/client-side-rendering/)

- On WebCodecs, there are a fair set of challenges, but we wanted to take the bet. The reason we're browser-based is the same reason I love Figma and Google Docs: no install, no waiting, just open and start. That said, for broader codec support (ProRes, RAW, etc.) we'll rely on server-side transcoding with proxies where needed.

We've played around with this and honestly have a lot of respect for what the Remotion team has built. Fun fact, I tinkered with it back in 2021 when they made those GitHub Wrapped videos, it was one of those projects that made me think differently about video on the web :) Cardboard is a bit different though, aimed at non-developers who want to edit raw footage through natural language without writing any code. Motion graphics is on the roadmap and Remotion would hopefully be a natural fit when we get there.

Cool to see the space evolving from so many directions! :)

I totally resonate with you. Craft takes time, and that's completely valid. We're not focused on filmmakers right now, though we'd love to have them eventually.

That's also why we built a full editor alongside the agentic experience. Use AI where it helps, like finding the right shot or removing silences, and do the rest manually. And if you'd rather finish in your editor of choice, we support XML export for Premiere, DaVinci, etc.

And agreed, there's really no substitute for the kind of intentionality Herzog brings to his work :)

Fair point. What we mean by collaboration is closer to how Figma works. From our user interviews, video creation almost always involves multiple people but in different ways: screenwriters, marketers, designers, directors reviewing the edit and sharing feedback.

The value might not be co-editing the timeline, it's making the feedback / iteration loops faster.

haha, good question.

My co-founder and I met in high school, and we wanted the name to carry a sense of craft. Cardboard was always that material in school projects that was firm enough to hold structure but malleable enough to build almost anything out of. That balance of structure and flexibility felt like a good metaphor for what we're building.

Also we just thought it was a cool name and bought a bunch of domains... https://cardboard.mov is one of my favorites :)

Totally fair reaction! Here's our honest thinking behind it.

We deliberately avoided credits/usage-based pricing because as founders using this in our own creative workflow, we hate the cognitive load that comes with it.

If I don't like a voiceover/variation, I should have the freedom to regenerate it until I'm happy without thinking about whether it's "worth" a credit.

That said, we could be wrong! Genuinely curious what you think would feel fair?

Sure! Will share the raw material for all the videos.

For some of the examples we shared though, we've created sample projects right within the product itself. They contain the raw assets and the exact prompts used to create the videos. You can try them out directly at https://demo.usecardboard.com and see the whole process!

Totally fair question. I've actually been a longtime Gecko/Firefox user myself, so this one stings a bit.

The short answer: Firefox doesn't support the File System Access API (https://caniuse.com/?search=File+System+Access+API).

We made a deliberate decision to go client-first. Video editing happens entirely in your browser without us uploading your entire footage on our end. No bandwidth costs for you, no storing your raw video on our servers. The File System Access API is what makes that possible, and unfortunately Firefox just doesn't have it yet.

It's not a forever thing though. For cloud-based projects where files live on our end anyway, Firefox support is very much on the roadmap. But for the local-first editing flow, our hands are a bit tied until Mozilla ships it.

Hope that makes sense, and fingers crossed Firefox adds support soon!

Thank you! You're right, there are so many subtle things to get right, appreciate the kind words. Crossfade's landing page looks slick btw!

my bad, I didn't test it enough on touch devices. Just pushed a fix, appreciate you flagging it!