4 ms·

Oh my goodness. I tried opening that sample app on mobile and it was like interacting with a touchscreen ticket machine from 2005. I don't know if it was just b

by rozab 6y ago

Oh my goodness. I tried opening that sample app on mobile and it was like interacting with a touchscreen ticket machine from 2005. I don't know if it was just broken on my browser (firefox android), or expects me to have the latest flagship to actually use it. Regarding the semantic HTML stuff, I don't think that's an issue inherent to the design, since flutter widgets tend to be highly semantic in nature. In fact, I think a platform like this could good for accessibility if it handles it properly instead of leaving it up to fallible developers.

nikkwong 6y ago
How though? All of the UI is rendered in a canvas element. This would break most existing screen readers and accessibility tools which rely on properly marked up and parseable HTML. I would suppose that the Flutter devs could provide some sort of bridge that would allow this to work (although I'm not sure how, unless the webkit team also steps in), but seems like an incredible amount of work and IMO with Google's history more likely to be abandoned than actually implemented.
jtsiskin 6y ago
Yes, I’m hoping it’s running in “dev mode” or something? Because even just scrolling on the latest iPhone was extremely low FPS and felt broken
- nikkwong 6y ago
  The state transition animations also happen to be very choppy even on my beefed up PC.
nv-vn 6y ago
Yes, the real criticism of this article should have focused on the hard-to-fix problem of performance because it seemed absolutely abysmal to me -- multiple seconds before the page showed up as anything but black on both Firefox & Chrome.
rektide 6y ago
> In fact, I think a platform like this could good for accessibility if it handles it properly instead of leaving it up to fallible developers. Fluttercs CanvasKit will never be good for accessibility because it will never work with the tools user's use on the rest of the web. Tools expect hypertext, expect a dom, & smashing that on the rocks & turning the web into VNCh no matter how hard the team tries- is going to result in the kind of accessibility that matches well & works across the rest of the web.

by rozab 6y ago

nikkwong 6y ago

How though? All of the UI is rendered in a canvas element. This would break most existing screen readers and accessibility tools which rely on properly marked up and parseable HTML. I would suppose that the Flutter devs could provide some sort of bridge that would allow this to work (although I'm not sure how, unless the webkit team also steps in), but seems like an incredible amount of work and IMO with Google's history more likely to be abandoned than actually implemented.

jtsiskin 6y ago

Yes, I’m hoping it’s running in “dev mode” or something? Because even just scrolling on the latest iPhone was extremely low FPS and felt broken

nikkwong 6y ago
The state transition animations also happen to be very choppy even on my beefed up PC.

nv-vn 6y ago

Yes, the real criticism of this article should have focused on the hard-to-fix problem of performance because it seemed absolutely abysmal to me -- multiple seconds before the page showed up as anything but black on both Firefox & Chrome.

rektide 6y ago

> In fact, I think a platform like this could good for accessibility if it handles it properly instead of leaving it up to fallible developers. Fluttercs CanvasKit will never be good for accessibility because it will never work with the tools user's use on the rest of the web. Tools expect hypertext, expect a dom, & smashing that on the rocks & turning the web into VNCh no matter how hard the team tries- is going to result in the kind of accessibility that matches well & works across the rest of the web.