1. Static linking is legally troublesome if you're distributing binaries because under the terms of the LGPL you have to allow for re-linking of your application. See ringworld's sibling comment on the Zoom app.
2. Even if you static link, you still need to build Qt for every single distro you want to ship your app on. On Linux the Qt GUI library alone has over 40 shared library dependencies. There are also ABI issues. Things like AppImage can help but are pretty nasty.
3. It's a lot easier on Windows and macOS, where there are fewer system dependencies and Qt Company themselves provide bundling tools (windeployqt, macdeployqt) to bundle libraries with your application.
Regarding 2. that is false, I build everything on a CentOS 7 docker and my appimage just works on every distro from that era onwards (~2015). Hy do you say that it's pretty nasty ? It's the same packaging mechanism than on Mac and Windows, the app ships everything except libc.
There's a linuxdeployqt tool for appimaged - I've never used it but saw a fair amount of apps using it I guess it works ?
2. Even if you static link, you still need to build Qt for every single distro you want to ship your app on. On Linux the Qt GUI library alone has over 40 shared library dependencies. There are also ABI issues. Things like AppImage can help but are pretty nasty.
3. It's a lot easier on Windows and macOS, where there are fewer system dependencies and Qt Company themselves provide bundling tools (windeployqt, macdeployqt) to bundle libraries with your application.