3 ms·
That's modern development for you. Shipping a copy of Skia so you can render exact facsimiles of Android widgets to a Vulkan context and avoid having Android re
by stefan_ 8y ago
That's modern development for you. Shipping a copy of Skia so you can render exact facsimiles of Android widgets to a Vulkan context and avoid having Android render Android widgets with Skia to a Vulkan context.
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).
- vvanders 8y agoFor 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.
- untog 8y agoI 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.
- discreteevent 8y agohttps://flutter.io/docs/development/accessibility-and-localization/accessibility https://flutter.io/docs/development/accessibility-and-locali...
- vvanders 8y agoOh 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.
- Apocryphon 8y agoSeems like some research and benchmarking into this potential issue is in order.