Whatever they're paying for it, it is too much. Video availability drops in and out. Sometimes the video works. Sometimes it doesn't work at all and gives a weird error. Sometimes it doesn't work and it claims that it "can't guarantee the security of my connection", even though other videos work fine. Sometimes videos that didn't work yesterday work today. I've been tempted to go to their app developer and try to show them how to just host it themselves in S3 or something, which would probably still be much cheaper than what Vimeo is charging. The Vimeo player embedded into the app is extremely minimalistic, for instance, it can't cast to anything, which is a pretty useful feature for something you don't want to be staring at your phone for.
I found I can Favorite a video, which then makes me log in to a Vimeo account, then it adds it as a Favorite to my Vimeo account despite being private, and then I can view it through the Vimeo app proper, although that also seems to have lost the ability to cast to anything in my house lately. Casting is a clusterfuck of its own with the mismatched capabilities matrix of what can cast to what under what circumstances anyhow, but Vimeo seems distinctly behind on that front. It's honestly significantly worse now than the default video player a browser offers at this point.
But it was probably relatively easy for them to set it up ~5 years ago, before Vimeo collapsed.
Once at Vimeo, maybe 7 or 8 years ago, I was working on putting out the fires of an extremely weird operational issue where a bug in a cloud provider's software-defined networking stack led to corrupted HTTP responses, which got stored in CDN caches, causing persistent playback issues for users (playback not starting, or locking up in the middle). The cloud provider had reported it as a "packet loss" issue, because for the most part the misdirected packets would get rejected by the receiving TCP stack for having the wrong sequence number or whatever, but one time in a billion they would get through and wreak havoc... and we were moving enough traffic that those one-in-a-billion flukes were happening constantly.
I was musing in the shared chat with one of our CDN partners that, with no real way to tell what files were affected, the only way to fix the playback issues for everyone (short of waiting a month for all the cached objects to age out) would be to simply purge the whole cache. I immediately got a bold all caps DON'T EVEN THINK ABOUT DOING THAT in response. If we flushed the whole cache, the origin traffic to refill it would have saturated some internet links to the point of DoSing other customers and probably getting on CNN that evening. And that was then. Traffic levels got significantly higher later on.
