Bizarre take. Notice how that WebGPU is an AndroidX library? That means WebGPU API support is built into apps via that library and runs on top of the system's Vulkan or OpenGL ES API.

Do you work for Google or an Android OEM? If not, you have no basis to make the claim that Android will cease updating Vulkan API support.

▲

pjmlp 2 hours ago | parent [-]

I did not do such claim.

WebGPU on Android runs on top of Vulkan.

If you knew about 3D programming on Android, you would know that there are ongoing efforts to have only Vulkan, with OpenGL ES on top.

However Java and Kotlin devs refuse to bother with the NDK for Vulkan, and keep reaching for OpenGL ES instead.

Please refer to Google talks on Vulkanised conferences.

▲

flohofwoe 2 hours ago | parent [-]

> ...efforts to have only Vulkan, with OpenGL ES on top...

Ok this made me laugh given that Vulkan support on Android is so bad that WebGPU needs a fallback mode to GLES ;)

https://github.com/gpuweb/gpuweb/issues/4266

	▲	pjmlp 2 hours ago \| parent [-]
		Agreed, which is Google's motivation for doing that. The argument being that if Android only does Vulkan, that OEMs will be forced to care about their drivers. There are talks done by Google on this, either Vulkanised, Google IO, or GDC, can't remember now the exact one.