dripsy VS rendertron

Dripsy unstyled UI primitives which are responsive (at the expense of SSR support though).

Here are libs to help you share code between web and mobile: - Shared UI primitives + style: https://github.com/nandorojo/dripsy

Try using dripsy. It allows you to create responsive themes a lot like the web.

Dripsy is a good solution for styling: https://github.com/nandorojo/dripsy

This article is extracted from this github discussion, which goes into greater detail on how to achieve this with the libraries Dripsy (a component design system) and Fresnel (SSR w/ media queries).

Does NOT currently support SSR. Even though it still works with NextJS for other reasons such as code splitting and navigation, and SSG.

Dripsy is very declarative: it allows you to provide object and array values to add mobile-first responsive styles. Instead of manually using the Dimension API (on native), and adding media queries and nested styles throughout your code (on web). This API is very inspired by Chakra UI's array syntax for declaring responsiveness. (Which Magnus UI also is inspired by).

Rendertron is deprecated

Please note that this project is deprecated. Dynamic rendering is not a recommended approach and there are better approaches to rendering on the web.

Rendertron will not be actively maintained at this point.

https://github.com/GoogleChrome/rendertron

GoogleChrome/Rendertron proxy https://github.com/GoogleChrome/rendertron.

Are you worried that rendertron isn't being maintained? (https://github.com/GoogleChrome/rendertron/issues/865 and https://github.com/GoogleChrome/rendertron/issues/801) Have you thought about using anything else or doing it yourself with Puppeteer or Playwright?

Rendertron, quite old now.

Googlebot: SSR a non-responsive mobile version only for the Googlebot User Agent, to get SEO. But do Client-Side Rendering (CSR) for users, to get full responsivity. Could be done with manual user-agent sniffing, or with a GoogleChrome/Rendertron proxy. Though Google may not like being fed something different than users (different initial markup, even though resulting markup after React’s first CSR should be the same). But it might be problematic long-term to SSR only for the Googlebot, since it’s effectively serving the Googlebot something else than what the users get.. Google might crack down on it, since it could be abused.

This might be another one: https://github.com/GoogleChrome/rendertron (not sure if it does everything that prerender does or not).

Still prefer CRA with Dynamic Rendering with rendertron over Next.js and Gatsby...

A demo Rendertron service is available at https://render-tron.appspot.com/. It is not designed to be used as a production endpoint. You can use it, but there are no uptime guarantees.