If you implemented client-side rendering authentication instead of SSR, what would you lose? Why was SSR chosen?

When implementing authorization through client-side rendering (CSR) instead of server-side rendering (SSR), we lose several important advantages:

• SEO and indexing: SSR allows serving a fully rendered page with completed authorization, which improves indexing and visibility in search engines. In CSR, content is generated on the client, which can hinder indexing.

• Speed of first display: SSR provides a faster initial page render, as the browser receives ready HTML. In CSR, JS loads first, which then renders the page — increasing the time to the first meaningful paint.

• Security: SSR allows more reliable processing and verification of authorization data on the server, reducing the risks of token leaks or forgery.

• Session management: SSR simplifies working with cookies and sessions, as the server can directly read and set them.

The decision to use SSR is made to improve UX through faster content display, increased security, and better SEO support, which is critical for many applications with authorization.