Colin pfp
Colin
@colin
@nickcherry what stack is the Warpcast web app using? Would love to hear about design decisions etc
2 replies
0 recast
0 reaction

Nick Cherry pfp
Nick Cherry
@nickcherry
Knowing that we would want OpenGraph support and eventually SEO, we seriously considered SSR solutions like Next and Remix. Ultimately, though, we felt that they introduced a fair amount of complexity with relatively little upside – the biggest benefit being "free" server-side rendering for OG and SEO.
1 reply
0 recast
0 reaction

Nick Cherry pfp
Nick Cherry
@nickcherry
A CSR solution was simpler and I would argue potentially more performant, but we still needed to solve the OG problem. We considered outsourcing the server-side rendering to someone like prerender.io, but we didn't love the idea of relying on a third-party, particularly when our product reqs weren't that demanding.
3 replies
0 recast
0 reaction

Nick Cherry pfp
Nick Cherry
@nickcherry
Ultimately, we ended up implementing a simple Next server (opting for the framework just for convenience of having out-of-the-box support for JSX) to live in parallel with the web app, which is all just client-side rendering. We configure Cloudflare to look at the incoming user agent, and route to the appropriate site
1 reply
0 recast
0 reaction

billzh pfp
billzh
@billzh
Great thread. Why do you think CSR is more performant in this use case?
1 reply
0 recast
0 reaction

Stas pfp
Stas
@stas
@nickcherry if it's still relevant, netlify comes with built-in prerendering https://docs.netlify.com/site-deploys/post-processing/prerendering/
0 reply
0 recast
0 reaction