Launched this week
Remix
Figma, but on your production app. Test variants and ship.
144 followers
Figma, but on your production app. Test variants and ship.
144 followers
Your whole team, experimenting on the real product. Remix lets any team member spin up a variant of your actual product: a safe, sandboxed copy you shape by prompting. No setup, no risk to production. Explore ideas side by side as a team. Like where two variants are headed? Drag one into the other to merge them. When an idea is ready, open a PR straight to GitHub. Every prompt is recorded, so reviewers see exactly how it was built and a live link lets anyone test before a single line hits main.
Remix
@heshamghandour The sandbox is what I'd want to understand before handing this to a support rep or a designer. When someone spins up a live copy of the real product, what is it running against: a snapshot of production data, seeded fixtures, or something synthetic?
Remix
@clement_avq Good question, and the honest answer is: none of the three by default. The sandbox runs the real app off the branch, what it talks to is a config decision you make, not something Remix picks for you.
For the case you're describing (support rep or designer poking at a live copy), I'd point it at a dev or staging backend.
They get a fully clickable version of the real product, and nothing they do touches production data.
The other options are there if you want them: point it at production if that's genuinely what you need, host a backend sandbox on Remix too so a frontend sandbox talks to its own isolated backend, or upload a build running on synthetic data.
Happy to walk through how you'd wire it up for your setup.
@heshamghandour Makes sense, thanks. One follow-up: is the backend target locked at the project level by whoever connects the repo, or can whoever creates a remix repoint it themselves?
Remix
@clement_avq Project level sets the default, and every remix inherits it. But each remix is its own VM sandbox, so you can repoint an individual one without touching the project config.
Think of it as a preset rather than a lock. Env vars are editable in settings, and you have full terminal access on the sandbox if you want to go further.
@heshamghandour Understood, so it's a default rather than a boundary. Given the target user is the non-engineer, is there a path to enforcing the target per role, and is repointing a sandbox visible to whoever owns the project?
I really like this, accelerating ideas -> prod while also giving the engineer greater visibility to see the whole process before the PR even lands, brilliant