Content
@
0 reply
0 recast
0 reaction
Stephan
@stephancill
is there a reason why "show more" can't just expand the cast in the feed instead of sending me to the detail view?
8 replies
0 recast
98 reactions
Dan Romero
@dwr.eth
It’s way faster to ship the nested view. Managing dynamic item height in a FlashList in React Native would require a lot of custom work. Twitter also does this fwiw
1 reply
0 recast
3 reactions
jtgi
@jtgi
🤝 https://warpcast.com/jtgi/0x80ade024
0 reply
0 recast
3 reactions
frdysk.framedl.eth
@frdysk
I've been struggling with this, especially when looking for the latest cast on that long counting thread on /count
1 reply
0 recast
2 reactions
Ryan J. Shaw
@rjs
I had a theory, but @clauswilke convinced me inline works better, and WC can handle the issue I raised with a hide/collapse button. https://warpcast.com/rjs/0x923a8566 https://warpcast.com/rjs/0x98f44ad7
0 reply
0 recast
0 reaction
Mikko
@mikkolagerstedt
This. Would be perfect. Maybe it can screw up the feed?
0 reply
0 recast
0 reaction
Charles Yoo-Naut
@cnaut
This is annoying in Twitter too. Really disrupts the flow of reading
0 reply
0 recast
0 reaction
nzrkk21
@nzrkk21
"Show more" may send you to the detail view instead of expanding the cast list in the feed due to: UX Design: Provides a focused experience and prevents clutter. Technical Constraints: Improves performance and simplifies code. Information Architecture: Allows richer, more detailed information. Analytics and Engagement: Tracks user engagement better. Design Preferences: Maintains a clean layout and focuses user attention.
0 reply
0 recast
0 reaction
Iamrav3n.eth
@iamrav3n
They are probably still working on it
0 reply
0 recast
0 reaction
