The tapping areas are, weirdly, super precise and not very intuitive or well explained. I would have gotten used to it but as a new user this was incredibly frustrating.
Can you expand on this?
I can try, but only to say the tapping behaviour wasn't intuitive. Depending where you tapped the comments would either collapse and expand or the vote controls would disappear. The tapping difference seemed, at first, quite similar (as in the tap area and sensitivity was really close and extremely high) so I had a hard time understanding what I was doing to cause these behaviours. What confused me more was that the behaviour between the home page and a thread didn't seem consistent at first which made it harder to understand.
Like I said I'm used to it now but it took me a while to get there where as I was expecting something like the following:
Bottom bar collapse exists the other way, some users prefer to not see the bar by default and then you can hold to show the bar.
I definitely wanted to make, tap/hold actions fully configureable. It's somewhere on the backlog, I'll create an issue if it doesn't have it already.
I liked click and hold to collapse (Reddit app style when I left Reddit)
I don't understand click once to collapse and click and hold to hide the voting bar. Why is hiding the voting bar a thing?
It's more the other way around, some ppl prefered, having the bar collapsed by default. And then hold to reveal it
What about long press to expand/collapse the chain and tap to show/hide the bar? Personally, most of my miss-clicks are attempts to click a link in the body. This results in everything collapsing and then needing to click to expand before trying again. I think it would be less frustrating if a miss-click of this type resulted in just the bar collapsing or expanding which doesn't hide the link that was missed.
I prefer making the action fully configureable (like even setting to nothing), over having a swap action setting.
Agreed. I have never intentionally collapsed a comment but done so many times accidentally. For all I care collapsing could be removed entirely.
Collapsing a hundred replies long comment chain is much better than trying to scroll and figure out where it ends. But it could be a (tap) menu item or something as it's not that often needed. And hiding the buttons? Maybe if you wanted to set up a screenshot or something but I don't see a user for it otherwise.
I like collapsing comments for when I'm not interested into anything in that thread.
But I agree the touch area for the buttons should probably be increased.
Enabling "show content for collapsed comments" helps as only the child comments will collapse upon tapping.
this works for me
thanks
I do actually like the tap-to-collapse feature. But instead of long-pressing on comments to get the voting bar, I'd rather right or left swipe them, similar to how BaconReader worked. The long press feels inefficient.
Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK0x400c96c96acbC6E7B3B43B1dc1BB446540a88A0141taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuVaddr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm