No-op on mobile / prohibitively small screens #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @wTheRockb, you may be right, but damn I like the exploding nodes! I'm going to leave this open for now to ponder what kind of experience I want on mobile - fast or cool, or something else? (looking forward to our call tomorrow) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Could consider not showing the graph while on mobile. Becase there are so many nodes, the d3 simulation takes a long time to settle with limited processing power (~40s on my pixel 5A). Additionally since there is no hover on mobile, user can't preview article title of the node, making it essentially a link to a random article.
After (fewer posts shown since I deleted a bunch to speed up build times while developing):
