Server-side rendering for Flutter web

Status: If your interest is in SEO, see https://github.com/flutter/flutter/issues/46789; otherwise, see https://github.com/flutter/flutter/issues/47600#issuecomment-1016920547. ---- As an app/web developer, I think Server-side rendering may offer a few advantages: 1. Easier search engine optimization. 2. Better loading time in some cases. Older devices may take a little longer to run the Javascript code. Also for applications that need to call a few REST APIs before rendering content, SSR may use caching to significantly reduce delay. 3. Better compatibility. Browsers still use different JS engines, therefore, rendering content from JS code on the front-end may sometimes get different results on different devices. Plain HTML will be much more likely to get rendered consistently. Is there any chance that Flutter web will support SSR in the future?

Posted by wliumelb on Dec 22, 2019, 2:00 AM

Tags

• support (SaaS)

Related issues

• I hate that this whole cluster of beliefs exists, but software on my own computer enforcing what I can and can't do for ideological reaso...
• As I replied in another comment[1], it's their software, their choice.
• [Feature] Support external model integration via personal API keys and local LLMs (BYOK)
• > So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
• Feature request: support multiple named accounts per app/connector
• Support standalone Windows installer (`codex-setup.exe`)