Animista: a collection of ready to use CSS animations
animista.net
animista.net
With that said, the website/webapp behaves kind of weirdly in my opinion. I would have never ever thought to click on the heart icon in order to select an animation for later download. I assumed that was some form of BS sharing feature. Also, when clicking on the "code" icon { } I wanted to see the underlying animation, not just its implementation.
If you use the "favorite" symbol/terminology then I'd expect to be able to browse a list of favorites somewhere.
One thing though, I've been clicking back and forth between this thread and the site and everytime I do I have to go through that animista loading image again. Got kind of annoying after a couple times. Maybe do something else, or just make it so it appears only the first time or something?
A tiny wee bit of an issue: Copying to clipboard does not work on firefox dev edition, had to get the code from source as selecting was disabled on the <pre>.
Also, why force downloading the whole library? Why not append the keyframes used to the code to be copied as an alt box entitled "Just want to use this one animation? Copy this!".
I don't understand the force downloading the whole library? I don't see that it does that. Going to the download page just provides me a way to copy the generated code of my chosen animations to paste wherever I want. I don't see an option to download anything.
Ah, I see now. Download is Chrome only. Regardless, my download only had the chosen animations. It didn't download the whole library for me.
You're right regarding the downloads! I must be super silly or this is slightly counter intuitive, didn't even notice the sidebar and the download page that requires you to "fav" animations first. And go figure, the copy button works there.
I can't find the license though, and won't push to prod until I do.
Animista is an awesome resource. Well presented and nicely done.
But if you think anyone can own the rights to specific transform values within the @keyframes rule, then you are mistaken.
That said...
Is it acceptable to animate `box-shadow` these days? Thought that was a pure framerate killer on mobile.
They do.
Well, as long as the browser of your choice supports the CSS properties in use. Which, at this point it would be easier to keep a list of browsers that do not support such things as opposed to ones that do.
It's just the site itself misbehaves on mobile. To test the animations on a phone, just tell your mobile browser to request the desktop site. You should be able to see the page then. More than likely that is, your experience may vary. I was able to see the desktop site on my Android phone. I was just unable to cycle through all the different animations to see them in action or choose them. That has more to do with how the UI of the site is built, nothing to do with the animations.
any small consulting job beats several thousand downloads
Animista lets people that write HTML/CSS/webapps interactively choose or tune the settings of a relatively small set of CSS animations styles. It's like a convenience table of contents for what one would typically find in scattered various CodePen examples. It wouldn't make much money.
It's "programmer think" to equate sellability with the number of icons/animation in the catalogue.
Edit: And even though it's not what I was saying, I don't know why you think that kind of thinking is 'programmer think'. That's a bit disparaging to programmers, no? The ones I know aren't that shallow.
$1k/mo > Any $/mo > $0/mo >>>> Negative $/mo spent on hosting
There are many people who would pay to use the code generated by this tool - even if it can be trivially grabbed via Inspect Element. It seems that's a common sentiment among posters on this topic - and I agree with them.
It might seem silly to charge for 3-step keyframes (0->40->100 on many of them) with different timing functions but people will pay for just that.
The CSS line for bouncing a box is already on a million other sites.
It's a nicely presented web app, I've bookmarked it. The donation model is more than enough.
Can't get any of it to work on my site. No instructions on how to make it work, other than copying the CSS.
Blerghhhh
What you download from Animista are just the keyframe definitions. You apply them to a target element using CSS properties, particularly "animation:"
They were giving pretty reasonable and, I dare say, obvious feedback. The site should provide an HTML snippet like just about every other demo page out there.
I can't see the author disagreeing with that.
You could copy and paste your "fuck them, right? /s" snark on just about every bit of feedback everywhere. I don't think that's very constructive, and it demonstrates a misreading of the parent comment.
Clicking on the icon `{.}` will slide out a div that contains the code for the CSS animation.
> Mobile version is unavailable at the moment. To experience Animista try it on your desktop.
The text is unselectable on mobile as well.
CSS animations work, any individual browser bugs notwithstanding. The nice thing about this site is that you don't have to guess all the CSS `@keyframes` and `animation` parameters to match some vision in your head, but you can visually experiment.
The actual value of this site is the interface, and I can see why it would be hard to make it work specifically for mobile devices.
The Animista web app is meant for web developers to browse the animations, take the very basic CSS code (not HTML) and use it in their projects - which might be mobile-friendly if you wish.
CSS animation is not "mobile or not", that task belongs to your other site-wide CSS and general HTML structure.
It's like saying you don't trust the drone will fly above 10 feet because in the store where you bought it the test flight was limited by a 10 foot ceiling.
That sounds like the happy expectations of someone free of the merciless grasp of deceitful vendors…
This is more like the store refusing to make the video demo of the drone on flight available to visitors using a mobile browser.
I just checked and while it loads on iPad, the top row of round buttons for animation category don't respond to touch.
Back to the analogy... it's more than a "demo drone video". It's an interactive drone experience where you select altitude and other settings and see the drone in virtual flight, then copy those settings to your own controller. Sounds like a task for a computer, not a phone.
Close... Product Manager (former Engineer) with 20+ years experience building things.
"You're either mobile first, or you're mobile last."
If someone puts up a warning sign telling me that they didn't bother to test their code on mobile... that tells me it's not ready for production yet. I don't want to get bogged down in something that wasn't tested on mobile, or that requires me to invest a lot of my time to get working right between browsers. Having the creator of this code put up a page saying not to use it on a phone seems to say they are comfortable writing off more than 50% of web users.
I don't think it's OK to launch anything, not even an MVP, if it doesn't work on mobile. Shouldn't building a mobile site be a trivial task for someone building CSS animations? How do I trust their work without a way to preview it?
All this site does is present existing CSS animation methods in a convenient, curated fashion with nice variations such as "wobble left". We know it works on mobile because the code is written according to the CSS spec.
If you have doubts about whether the CSS animation works on mobile, then you have doubts about whether the CSS animation spec in general works on mobile.
Developers don't copy and paste and write code on their mobile phones. Therefore the target audience is not your "50% of web users" club, which is a consumption stat, not coding or technical productivity/creating.
The code that you take from this site goes to your own project, and that's when you test on mobile - with your own HTML elements and other code.
Finally, "mobile first" is not right. Nothing should be "first" because by definition everything else is given less priority which is flawed logic depending on the application. "Mobile-friendly" is the more sensible idea.
You are not entitled to "Mobile First" just because a conga line of over-memed industry bloggers repeatedly insist we are entitled to all the content on the internet through our mobile browsers.
You're waving your phone around like it's attached permanently to your hand, and the only way you can get online!
The site responds and tells you what's going on. There is no fault. Be patient, be cool, save the bookmark and check it our later.
Don't be the kid throwing a tantrum because the hand-me-down phone you got for Christmas doesn't run Pokemon Go.
Screen size is an inherent limitation of mobile, always will be. Video editing, photo-editing, anything requiring a complex interface on a single page, or anything the developer hasn't released yet for reasons which are their business.
Giving release priority to desktop (including laptop) for a technical development app is OKAY in 2017. Just breath, everything is okay. The site is trustworthy, the code is trustworthy.