trending

1d ago

Why I built Frontloop: our designer's 5-minute fix took 3 weeks to ship

A designer on a team I worked with spotted a misaligned CTA. The fix was one line of CSS. It shipped n weeks later -- after a ticket, sprint planning, and two status pings.

That gap between seeing a UI problem and shipping the fix is what Frontloop is for. You open your live product, point at what's wrong, describe the change in plain words, and it opens a pull request your engineers review and merge. Engineers keep full control -- they scope what's editable, and every change goes through normal review.

1d ago

Engineers: what would it take for you to let non-engineers open PRs on your repo?

Serious question for the engineers here. Frontloop lets designers, PMs, and founders make UI changes by pointing at the live product and describing the change in plain words each change lands as a PR on its own branch for you to review.

We designed it assuming you'd be skeptical: the engine is open source so you can audit exactly what it does, you scope which routes and files are editable, and nothing merges without your review.

6h ago

Frontloop - Change the UI yourself. Your engineers approve it.

Frontloop runs your live product in the browser. Point at anything that looks wrong, describe the fix in plain words, and it writes the code and opens a pull request your engineers review and merge. Changes land on separate branches, engineers scope what's editable, and nothing ships without review. Works with React, Vue, Svelte, Next.js, and Angular. The engine is open source — audit it or self-host it.