So I'm currently facing a problem where a logged-in user should be able to do 2 (completely) different actions on 1 page (view):
Respond to "product-requests" (searches from other users)
Is it possible, based on your experience, to enable these completely opposite kinds of behavior in one view, without lowering priority for one of them?
Or should you always create focus for the user and focus on 1 primary intended action and make the other behavior secondary?
One of the ideas I had, was making a clear distinction in the scroll-direction for the different types of behavior.
Where the requests can be seen as an inbox, you can go through horionztally at the top of your view: Giving you the opportunity to skip them easily or respond to them.
And if you want to browse, you scroll vertically a well-known pattern for endless browsing, giving the opportunity to add a "infinite scroll"-feel to the list of products.