NeoApplications
Prevent app sheet from being closed by scrolling up
With 1.0.0 through 1.0.2, I frequently happen to close an app details sheet inadvertantly by scrolling up a little too far.
If the app details sheet has been opened from one of the app listings (explore, search results etc.), the app then needs to be identified there and tapped again to get back to its details view.
If the app details sheet has instead been opened via (a sequence of) links in other apps' details views - like the second app in the screen recording below -, getting back to the closed app details is more elaborate.
Screen recording
https://github.com/NeoApplications/Neo-Store/assets/15276963/96415cec-7b2f-49bd-b79c-ee496d534e21
Unfortunately, this issue is aggravated by choppy scrolling even on a reasonably powerful phone, see the tap marker's movement vs. scrolling in the screen recording. Note that the stuttering is not caused by the recorder but by Neo Store's own GUI performance, which the video depicts rather realistically.
Touch interaction would be slowed down just too much if every tap or scrolling increment had to be waited for to complete before proceeding. Therefore, keeping touch input in sync with the displayed scrolling state, in order to immediately recognize the moment when scrolling further up turns into closing the sheet entirely, would be impractical.
Of course, a direct, smooth scrolling experience would be much preferrable, and possibly also reduce this issue to a minor inconvenience.
However, given the real (current) state of affairs, it would help a lot if app sheets couldn't be closed by swipe downs.
I forgot to mention there's a similar problem with the search results list. If you're further down the list and quickly scroll all the way up to the top, it's too easy to overscroll and inadvertantly close the entire search results list.
I suppose the technical reason is the same, so I'm just adding this comment rather than a separate issue about this.
choppy scrolling even on a reasonably powerful phone Can you please define what is this "reasonably powerful phone" exactly? Furthermore, can it be that you have set a low system animation speed?
And into the blocking the dismiss gesture: It's what a user would expect when working with a sheet. That said, I'll see and survey the community's opinion when working on future minor/major releases in this matter.
Can you please define what is this "reasonably powerful phone" exactly? Furthermore, can it be that you have set a low system animation speed?
I'm referring to the better one of the devices also mentioned in #593, which is a Qualcomm 660 octa core, 6 GiB RAM, Android 11 phone. On the older one (Samsung J3), it's worse.
Regarding animation speed, I can't find that exact setting, but Window animation scale, Transition animation scale and Animator duration scale (all in developer settings) are all set to '1x'. Moreover, there's no issue with scrolling in other apps, and there was none in pre-1.0.0 either. In fact, interaction with the vast majority of 200+ other apps generally feels nice and fluent on this phone.
And into the blocking the dismiss gesture: It's what a user would expect when working with a sheet. That said, I'll see and survey the community's opinion when working on future minor/major releases in this matter.
Just to be clear, I'm not suggesting to remove the dismiss gesture all together but to give users the means to disable it. That's especially needed if it cannot be separated reliably from scolling up, and those sheets can perfectly be closed by the back button.(*) After all, user expectations (or conceptions/assumptions thereof) are one thing, real life usability is another. It's the users who run into what doesn't work for them or what really does, and should be able to choose the latter.(**)
That being said, thank you for actually listening to the user base - as well as for the already great app in general! I'm obviously not filing issues to express appreciation or acclamation (even though it'd like to do that) but to help further improving NeoStore. My attempts to contribute to this particular app are largely based on just how useful, cute and enjoyable it already is.