I’m going to “third” the above post concerning Raspberry Pi support.
My partner is an educator and her district requires using Zoom to meet with students. For reasons not relevant to the discussion, she uses a Raspberry Pi (recently upgraded from a Pi3 to a Pi4) as her home computer. To date she has been using a very restrictive and unstable arrangement of a myriad devices that’s far from ideal, extremely unreliable, and totally impractical.
The only way she can use Zoom on the Pi is through the web-based version in the browser; in her case, Chromium (Chrome). However, that method is unstable because the tab hosting the session crashes. That requires reloading the tab. Furthermore, on starting a session, there is substantial lag between the time everything loads, and when the “connect” button becomes clickable (20-50 seconds). It’s one thing when you’re hosting and/or are setting up ahead of time, but quite another if the tab crashes mid-session.
Unfortunately, because of the school district’s Zoom requirement, she cannot use another platform that is not only stable, but also supported by the armhf and aarch64 architectures. She’s kind-of stuck. Unspoken in all of this is that she is doing all of this with a combination of visual disabilities that makes everything even more difficult for her.
But back to the Raspberry Pi: “A bunch of people…who want a RPI-compatible Zoom client” is just the tip of the iceberg. That merely refers to the people discussing it in the aforementioned Pi forums. Since its initial release, as many as 30 million Pi units have been sold worldwide as of December, 2019. This number, which keeps growing, should be another motivation for Zoom to produce a native Pi/armhf/aarch64 client. The aforementioned bunch of people are not the only ones who stand to benefit from it.