Re:Google's cross-platform Flutter UI toolkit goes 1.0
by vvanders on Tuesday December 04, 2018 @01:32PM
(#18602233)
For bonus points you've probably broken accessibility on many platforms as the way that a11y works is intrinsic to the native widgets used by a platform.
Re:Google's cross-platform Flutter UI toolkit goes 1.0
by untog on Tuesday December 04, 2018 @02:31PM
(#18602875)
I wouldn't assume that. It's literally the number one thing people bring up with custom UI components, I'd be very surprised if Flutter ignored the issue.
Re:Google's cross-platform Flutter UI toolkit goes 1.0
by discreteevent on Tuesday December 04, 2018 @03:06PM
(#18603159)
Re:Google's cross-platform Flutter UI toolkit goes 1.0
by vvanders on Tuesday December 04, 2018 @03:34PM
(#18603345)
Oh I'm sure they didn't ignore is, just that you're constrained to platforms that allow a side-channel mechanism to expose a11y and handle focus+navigation.
I haven't looked deeply at the HTML5 APIs but if you wanted to say port Flutter to HTML5 Canvas you may run into problems where you can't expose rich enough a11y primitives on something that was just meant to be a bitmap.
Re:Google's cross-platform Flutter UI toolkit goes 1.0
by Apocryphon on Tuesday December 04, 2018 @02:52PM
(#18603047)
Seems like some research and benchmarking into this potential issue is in order.
A full Chrome copy for your desktop app is whatever, we have the resources, but on smartphones this is actively harmful. It bypasses the hardware compositors. Displaying a video, they have to render that to a graphics texture; on many smartphones, the IP that is doing hardware video decoding has nothing to do with the GPU and they might very well not use the same formats, requiring CPU conversion (if it's at all possible).