3 ms·
I'd have to disagree with all of those points. The background transitions first, then the foreground content transitions afterwards; they're not all moving at o
by prophesi 8y ago
I'd have to disagree with all of those points. The background transitions first, then the foreground content transitions afterwards; they're not all moving at once. The foreground content then remains stable once the transition finishes. Perhaps some opacity could be applied to the foreground content to discourage users from trying to read while it transitions.
And it makes sense to have the history change with each slide state. Describing it as a 'state' upholds that point. The back button even works with it, which is my main gripe when single-page apps don't 'pollute' the browser's history.
- uxcolumbo 8y agoCheck again - for me some of the videos play at the same time while the page is still transitioning... that's what I meant. To me that component on the homepage is more like a 'carousel', so when I hit back I expected to be back on HN, but instead I stepped through each slide again with all the transitioning. But it doesn't matter what my or your opinion is... we both have different expectations and all I'm saying is ideally this stuff should have been tested with more users.
- prophesi 8y agoYes, all of the videos should be auto-playing. I'm saying that the discomfort would likely be alleviated if the text's opacity transitioned in. Then you should be able to handle the awesome rippling effects. And my guess is that your expectation for the back button to send you back to HN is because of how the majority of SPA's break the back button. It's a disheartening reality. I understand the importance of testing with actual users, but it's honestly pretty amazing that these are the only broken expectations for a portfolio site like this.