121–130 of 162 posts
Scrolling through that landing page felt a lot smoother & snappier than I would've expected for a page looking like that.
Do they explain how they made the landing page or share the code somewhere? I agree, it's stunning.
Earlier quoted context omitted.
It's clever, but honestly I don't care how smooth it is. Scrolling should simply scroll a view up or down a page. Not invoke animation. We already have established UX patterns for playing media, slowing it down, speeding it up, randomly seeking through it.
Part of the smoothness here is that scrolling the text is 1:1 once you get down to the sections with colored headers. It demonstrates that it's possible to make a page look fancy like that without "breaking" your intuition of what scrolling "should be." JS animations obviously don't take the place of video/audio media that you'd play/scrub through.
I cannot believe this is real, it was so well done. It felt like creativity of the internet from the early 2000s met the polished design standards of today.
Earlier quoted context omitted.
Do they explain how they made the landing page or share the code somewhere? I agree, it's stunning.
Hey I'm the author of the lib, I'm thinking about making a course on how to re-create the landing page, would that be something you're interested in?
Devs, please don't use this. it is unusable for me when browsing in a VM with a pretty snappy internet connection. The only other site that has compute/graphics resource issues for me is Netflix (its competition Prime, Youtube,etc.. have no issues, so i can only presume bad software dev decisions).
This has nothing to do with internet connection and everything to do with hardware accelerated graphics.
Earlier quoted context omitted.
Do they explain how they made the landing page or share the code somewhere? I agree, it's stunning.
Hey I'm the author of the lib, I'm thinking about making a course on how to re-create the landing page, would that be something you're interested in?
Earlier quoted context omitted.
Do they explain how they made the landing page or share the code somewhere? I agree, it's stunning.
Hey I'm the author of the lib, I'm thinking about making a course on how to re-create the landing page, would that be something you're interested in?
Earlier quoted context omitted.
Do they explain how they made the landing page or share the code somewhere? I agree, it's stunning.
Hey I'm the author of the lib, I'm thinking about making a course on how to re-create the landing page, would that be something you're interested in?
Still waiting for the WYSIWYG GUI-base authoring tool for a web animation API. You know what artists - animators - generally don't like? Wading through docs and code to spin a square. It's been about a decade since the average of the various watersheds in the slow death of Flash, and we still don't have a replacement.
https://docs.godotengine.org/en/stable/tutorials/animation/i...
Earlier quoted context omitted.
This has nothing to do with internet connection and everything to do with hardware accelerated graphics.
I understand that, I meant they made the choice to use power and resources on the client end when internet bandwidth is abundant and they can utilize server resources for cpu intensive workload. Design choices such as these are exclude anyone who can't afford decent hardware and are inefficient in terms of power/energy usage.
I feel it's totally within scope for an animation-focused library to expect clients to have GPU hardware acceleration. The fact you're running in an isolated environment, and haven't configured it to be able to use your host machine's GPU (which is possible!), feels niche enough to me to write off.