Calling developers checking HN on their phones "web dev 101" is pretty condescending. Give the benefit of the doubt, and assume they are engineers with limited time to check out new technology and are disappointed that they can't view these animations while riding a bus.
I was responding to the person who said they didn't have confidence using the CSS in their mobile projects because the site where they got the code from didn't work on mobile. That's not the logic of an engineer!
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.
> 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.
If you have Firefox for Android you can tap "request desktop site" if you really wanted to see the site on your phone. If you have an iPhone, I guess you're out of luck.
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.
Your analogy doesn't make sense. The site shows animations which work on mobile, but won't let people on phones view the animations. That puts up a barrier to adoption: even if there are a ton of fiddly UI widgets to control the animation, the mobile site could show a default animation & say, "click here to customize this animation (desktop recommended, lots of controls that don't work well with touch)".