This is an amazing book, I so like that Google give it for free.
My question. There are any drawback of using HTML render instead of CanvasKIT?
Is there are showing the user the exact same UI? Or HTML render still have bugs?
This is an amazing book, I so like that Google give it for free.
My question. There are any drawback of using HTML render instead of CanvasKIT?
Is there are showing the user the exact same UI? Or HTML render still have bugs?
Hi @aminadav thanks for your feedback!
Both web renders aim to exactly show the user the same UI.
Based on my experience with deploying Flutter to web, i prefer using the HTML render mode because it seems more stable and responsive on web. Under the hood it uses HTML elements, CSS, and canvas elements and has a smaller download size.
As for CanvasKit renderer i prefer to use this on mobile and desktop. The responsiveness is just night and day comparison!
In 2022 i believe the Flutter team is focus on improving Flutter web’s performance, making it feel more native for web and support for SEO.
Check out their article for what’s to come:
This article list all the issues they are aware of, and hopefully they address them sometime this year!
Thank you very much! interesting. We’ll read.
I’ve been following this discussion with interest! From what I understand, both HTML and CanvasKit renderers aim to provide a consistent UI experience. However, HTML renderer seems to be preferred for web deployments due to its stability and smaller download size, while CanvasKit might be better suited for mobile and desktop due to its responsiveness. It’s great to hear that the Flutter team is focusing on improving web performance and SEO support. I’m curious if anyone has experienced any specific challenges or advantages with either renderer in their projects?