Post

Isomorphic SSR

Whatever NextJS is. Does React even exists outside of NextJS? ;)

CSR, no SSR

CSR, no SSR

CSR

CSR

Isomorphic SSR, but mostly CSR. Tried RSC, but found the transition in Next to be impossible to do gradually. Too many API incompatibilities. Will likely abandon Next rather than upgrade.

RSC We currently have 3 projects all on rsc. Two are just marketing sites and one is a proper app. For marketing sites it’s all good but for our app I dream about rewriting it entirely in either vue or svelte. Next really left a bad taste. One of these nights I’m gonna take the plunge…

CSR

Isomorphic SSR

CSR, no SSR

CSR by some distance.

CSR and Isomorphic (using Remix)

We build an app to consolidate and manage information previously stored on paper records.

Nope!

CSR with a very tiny hint of SSG

CSR

CSR

RSC

Closest to Isomorphic SSR, but quite atypical!

CSR and SSR

Isomorphic SSR

Two apps for the company I work at, both entirely CSR.

Full CSR, micro frontends environment

CSR with lots of data-wrangling on the backend to unload the FE.

Isomorphic SSR with Vike 💪 (shout out for @brillout.bsky.social)

CSR, no SSR

RSC and isomorphic SSR

RSC

RSC - a medium-sized open education project. Next.js 15, drizzle, postgres. We like it a lot.

CSR

CSR, that’s what Sanity Studio. I don’t know if starter templates and demos counts? Even if they are it’s overwhelmingly CSR across the line

RSC

SSR public pages, CSR app

CSR, no SSR

RSC + isomorphic SSR (Next.js app, App Router w/ RSCs for "new" pages, Pages Router for "old" pages)

CSR, no SSR

How do you categorize SSG? Build-time SSR then CSR covers so many use cases. A lot of websites are a bunch of public-facing marketing/SEO pages + a logged-in CSR app.

I make a wrapper component for a SolidJS component.

CSR, no SSR

CSR and multiple of them

Before I got layed off, I greenfielded a CSR, No SSR React project (used Tanstack Router) Another team chose Django with HTMX for their new project. Where does that fall, Isomorphic SSR?

Maybe one day we'll have SSR/dynamic SSR & prerendering at Datadog, but as most of the content id highly dynamic, we only do CSR for now

CSR

Csr

CSR

We do Isomorphic SSR @crunchydata.com using Remix.

CSR mostly dashboards.

CSR. But looking for a way to leverage some SSR in the future, for perf critical areas.

SSR with Remix

NextJS all CSR, exporting into html files and copying pasting into wordpress

CSR

Over my last 8 years, CSR only. Even some features should be use SSR, our team still do CSR. So I always keep an eye on Tanstack Start because of "Client-Side First, 100% Server Capable" 🥳

Currently CSR, no SSR.

csr

CSR, no SSR

CSR, no SSR

- ported dashboard to RSCs with PPR, reducing LCP by 100ms for dozens of 30 minute sessions per week

CSR Migrating part of an app from ASP.NET to React, and a SPA was by the easiest solution because we can leave the existing backend as is.

Csr only

CSR, but also RN

CSR, no SSR

So many CSR only in replies! Web Almanac has a sampling bias in that none of the dashboards behind a login is visible to these tools.

I did work on SSR

RSC

CSR

Isomorphic SSR

CSR with some SSR components.

RSC

CSR, and no regrets tbh

i write microfrontends, apps on a larger legacy page all CSR, rarely nested workflows outside of the occasional modal lots lots lots of forms

CSR but slowly moving towards SSR

CSR

CSR only

It depend on projects, CSR most of the time but I worked on SSR projects too.

Moving from SSR to RSC

CSR, no SSR I would *like* to have SSR for user generated content that is public however, so it can be indexed. But that isn't a priority

CSR and SSR. The CSR project has a much greater impact which I attribute in part to the fact that it's CSR but mainly to the fact that it's my own solo project. The SSR projects are the main job of my team but I have to say that I would do things differently if I could.

Iso

CSR, No SSR (React Native)

RSC

Hybrid CSR + RSC React Native app (Yes, we are using RSC in react native in production. Hoping to adopt Expo Router soon)

Mixed CSR/SSR, with an initiative to be all Isomorphic SSR

Mainly CSR, but lots of "grey area" with Next/Gatsby. Typically SSG and hydrated in those contexts. Tried one thing with RSC with Next and burned it to the ground, migrated to Svelte 😅

isomorphic SSR in next.js marketing sites

CSR, no SSR.

Took a lot of work, but now RSC

RSC

I get paid to work on Next V14. We are using server components and app router.

A CSR CRM

CSR, no SSR

CSR, no SSR

CSR and using Wordpress (so importing from WP’s @wordpress/element package vs react.

isomorphic ssr. i work on internal tools and there's always an ask for apis. it's easier to consume apis from a react app and less overhead with onboarding other devs that only care about enough react to get the job done.

CSR, no SSR

Isomorphic SSR, though currently thinning it out and migrating most parts to CSR

CSR

CSR mostly

CSR, only a single Next JS full stack app over 4 years of React dev

CSR, no SSR

CSR

CSR

Csr, no ssr

Next.js works quite well with this setup tbh. Using the middleware and the route.ts routes that it offers, a lot of code that should be handled server-side, is handled server side.

CSR

CSR, no SSR

Over my career (8 years): CSR made the most money Last 3 years alone: SSR (Next.js pages router) Last 6 months alone: RSC (Next.js app router) A small sample, but business decisions have often been driven by the general ecosystem direction.

RSC

Isomorphic SSR

CSR, no SSR

CSR

CSR

CSR. Won't get to do server stuff for another 1-2 years

CSR, no SSR

CSR

CSR

CSR

CSR

Oh and for the record the rebuild wasn’t to update the next version, that is just a happy side effect. The change is more driven by infrastructure issues.

Isomorphic, Remix

CSR, no SSR

CSR

SSR

CSR, no SSR