That’s still very unreasonably large and is going to cause real problems for some users, though not as many (and is still going to be uselessly slow to load for many—much of the world, including where large numbers of developers, even SwiftUI developers, are, doesn’t have multi-megabit-per-second speeds). Look, even 20MB is too large. Please, I beg you, just don’t put any GIFs on that page: just make it clear that it’s a video, e.g. by overlaying a circled play icon on the image and making it a link to the relevant video on YouTube.
No, don’t put it in the title, just fix the page. A page being even 100MB would be wildly unacceptable, let alone 450MB.
The really quick fix is just to replace the images with links to the images. Anything fancier (like replacing them with static images and links to actual videos rather than GIFs) can come later.
Please. I’m not trying to be mean in any way, but words are failing me at just how bad this is. You just don’t do this sort of thing. Entirely genuinely, you have probably directly cost at least a dozen people a few dollars with these GIFs, and measurably (sometimes seriously) inconvenienced dozens more for up to a month due to limits reached or approached.
The documentation for the iOS Sdk is terrible. It's also in Obj-c. The Web API is pretty clear and we all love JSON. The only thing I could see myself using the iOS Sdk for is remote playing.
In that case, what license should I change to? As long as others who want to release an app based on my source code consults me about it, I will let them.
