Why I’m Leaving the Remix Team (and What the Past Year Accomplished)

After roughly ten months as Director of Developer Experience at Remix, I’m stepping away from the day-to-day role. My focus is shifting entirely to a new project, EpicWeb.dev, which will still lean heavily on Remix. I’m not leaving the community — just the payroll.

My personal mission has always been “helping people make the world a better place through quality software.” When I joined Remix, that meant building a community around what I believed was the framework leading the way for future web development. That conviction formed after I rebuilt my own site with Remix, and it’s been validated by how many modern frameworks have since adopted ideas Remix pioneered.

Community growth in numbers

Looking back, the community building was intentional and the results speak for themselves. By the numbers, Remix has grown faster than any web framework before it — even accounting for its initial period as paid, licensed software:

  • 13k members on the Remix Discord.
  • 2.4k members on Meetup.com across 12 groups in 10 countries.
  • The inaugural Remix Conf in May 2022 sold out with 300+ attendees and 31 sponsors, just six months after open sourcing. The workshop drew 80 attendees with 80+ on the waitlist. Remix Conf 2023 is already scheduled for May 9–11.
  • 429 contributors on GitHub.
  • 12.5k public projects on GitHub using Remix.
  • 8.4k downloads across 12 episodes of the Remix Podcast.
  • 2.7 million views by 673.6k visitors on the Remix website.
  • “Breakthrough of the year” award at React Summit 2022.
  • 10.3k YouTube subscribers with 426.3k views (and 52.8k hours watched).
  • 19.4k newsletter subscribers.
  • 42.7k followers on Twitter at @remix_run.
  • 74k weekly downloads of @remix-run/server-runtime.

Adoption is harder to quantify, but thousands of companies are now using Remix in greenfield and migration projects alike. I can’t name most of them, though it’s fair to say a few start with “N” and end with “etflix,” “M” and end with “icrosoft,” and “T” and end with “esla.”

What I actually did

My time went into pushing those metrics and the underlying quality of the DX. I gave my introductory Remix talk over 20 times, including at many of those larger companies, traveled to six conferences, and appeared on over 15 podcasts and interviews.

On the technical side, I played a primary role in developing and designing the Remix CLI and the Stacks feature. I sped up Remix’s own test runs 2x, created a local development playground for the framework, and built the Discord bot. I pushed 113 commits to the repository, merged 485 PRs (mostly docs and examples), and was deeply involved in discussions across the repo, Discord, and Twitter.

As a cofounder, I met weekly with Ryan and Michael to set company direction. A newer responsibility was leading other developers at Remix to implement fixes and features — I’m not a natural manager, but nobody quit, so I’ll count that as a win.

The trends are more exciting than the snapshot above suggests. I’m proud of what the community has become, and I’ve never felt more productive building for the web. For specifics on the new venture, see the companion post, I’m Building EpicWeb.dev.