When rapidly scrolling down, for example, the posts on someone's account, I found it very easy to accidentally swipe back to the previous page. This is particularly bad because there is no way to swipe back forward, at least that I know of, and in the case of the example, when you open the profile again, it resets back to the top, which is terribly inconvenient if you're looking for a Tweet they made a particularly long time ago and they've tweeted a lot since then.
I would chalk this up to a problem with how I scroll my finger on the screen, if it weren't for the fact that I ONLY have this problem on this app. I also use YouTube and Apollo frequently, and I never accidentally swipe back in those.
I think it's a problem with how it is possible to trigger it - in those two apps you can only swipe back when you actually touch the far left edge of the screen. In Twitter this requirement isn't present. Obviously the easiest method to fix this would be to implement this requirement, or if that's not possible for whatever reason, find some way of reducing the sensitivity of this.
When rapidly scrolling down, for example, the posts on someone's account, I found it very easy to accidentally swipe back to the previous page. This is particularly bad because there is no way to swipe back forward, at least that I know of, and in the case of the example, when you open the profile again, it resets back to the top, which is terribly inconvenient if you're looking for a Tweet they made a particularly long time ago and they've tweeted a lot since then.
I would chalk this up to a problem with how I scroll my finger on the screen, if it weren't for the fact that I ONLY have this problem on this app. I also use YouTube and Apollo frequently, and I never accidentally swipe back in those.
I think it's a problem with how it is possible to trigger it - in those two apps you can only swipe back when you actually touch the far left edge of the screen. In Twitter this requirement isn't present. Obviously the easiest method to fix this would be to implement this requirement, or if that's not possible for whatever reason, find some way of reducing the sensitivity of this.