Because they’re meant for the web, there are very few frames. I have to allow enough time after the page loads, and before the animation plays, for all the frames to get loaded. For that reason there’s a very simple animation that plays first, and there are only two animations on each page.
There are usually two things going on in each animation. There’s a primary motion that carries the element around the page, and a secondary action that’s sometimes a limited animation within the element, and sometimes a special effect.
The site’s page layout responds to the browser window’s width and it changes any time the window’s resized. That did lead to some conceptual weirdness. I can’t predict how large the browser window is, or whether its size may change between one frame and the next. In some cases I had to deal with unexpected outcomes when I resized the browser.
Everything seems to work now. There’s just one case – an element that travels along an arc – in which phones may have trouble keeping up with the frame rate. I can’t test that because I don’t use a mobile phone. But the math in that one instance is fairly intense; I don’t think any of the other animations will present a problem.
And I may even do one or two more before you get a chance to see them. But, honestly, this was just a twelve-day obsession. I really ought to be working on something else. It’s just that it’s nearly impossible for me to leave something alone when it almost, almost works.