Hitting the Discover icon while on discover page enters the search page+ keyboard & if the discover icon is hit again or the search page is left it reloads the Discover page 🤔 ❤️

[CookieyedCodes]

Little things to tighten up the app, so I don't have to move my hand every time 😅 😉 ❤️

[mchowning]

Interesting idea. 😄 A couple of possible concerns come to mind.

It might be a bit confusing to a user who tapped the discover icon twice by accident. We could add a debounce to avoid accidental double taps, but that would probably just frustrate users who wanted to double tap to open the search.

Also, once the search page with the keyboard is loaded, the Discover icon isn't visible anymore because the keyboard is covering it to leave room for search results, so it wouldn't be possible to just tap the icon again to go back to the full discover view.

[CookieyedCodes]

It's interesting because I personally wouldn't find it confusing mainly because Spotify dose this (it's the only thing I find they do better tbh XD) +also I think your iOS app dose this in some regards too tho I might be misrembering+ most android apps have a dedicated button to hide the keyboard & hitting search dose wipe the keyboard tho ++hitting back gesture or the back icon will still be their and should further avoid confusion until more users realize the secret++

I would agree to a deadzone which would kill the keyboard -maby a 2 finger swipe on the search area is my only thought 🤔- tho it's slightly less annoying with 7.24+? because of the fixed bottom bar/keyboard buttons again I really only want to move my hand to the top of the screen when I am doing multiselect hence my niggle 😂

[CookieyedCodes]

Oh ignore the two finger swipe gesture it's not needed as sliding through the list drops the keyboard so hmmmmm

[ashiagr]

I was thinking about adding a pull-to-refresh as an explicit action to refresh the Discover screen. This will de-link the Discover tab from the refresh action and allow it to act as a shortcut to show the search screen on double tap. Wdyt?

[CookieyedCodes]

If refresh is not possible on a return to a page? that is fair enough to I would find it weird considering browsers can do it, you do make me think that pull to search might be a better action tho (might be better action once people get used to it tbc because it gives the user time to think & is quicker as tada keyboard 🤔 & dosen't disrupt the refresh) ++ you want to keep your refreshes up
But whichever truthfully either is an enhancement in my eyes :)

[ashiagr]

It is definitely possible. But considering search is a more frequent action as compared to discover updates, there will be unnecessary too many requests to the server which I wanted to avoid.

[CookieyedCodes]

Which is a fair point (I know why you want the discover refreshes as that helps with spon but it should probably refresh at least once a week regardless of refresh, maby you could get it to force a refresh once something has changed on the page, unless theirs something I'm not accounting for),

Either which way tho it will be an improvement in my books, I hate unnecessary hand stretch 😭