I do have pages of wishlists. I used to go to any store, and on right side of the page under " Your Wishlists" I would get everything that the store would have. Now it only shows 15 wishlists max, and I've confirmed that the store has parts in my other wishlists that don't appear on the shop homepage in the list of 15. This changed for me sometime in the last week. Anyone else seeing this?
Comments
Is this related to the changes you made?
@Stellar yes, I will probably need to build a "show more"
I also appreciate that for every user that mentions a pain point, there will be many that experience it but do not mention it.
@Lawrence Mine truly was a "pain point" for me. I had a bandage on my finger as I was trying to type.
Thank you for fixing it!
I don't know where the tradeoff between having one wishlist with 1200 items versus having 100 wishlists with 12 items each…how that impacts how fast the server can respond to a particular page load…but the current implementation without "all" and having to deal with "show more" "hide more" makes the browsing efficiency…that is the time it takes for the user to drag the cursor around the screen and click to reveal a hidden item, then scroll some more to locate the desired target…much worse than waiting an extra second (which I can say I was not experiencing) for the page to load.
I don't know what the answer to the issue here may be, but I can absolutely state that user efficiency is taking a massive hit with this implementation.
For me, with 60+ wish lists, this change means I have gone from needing to click one "all" link to reveal all items a store has to either:
one click plus one scroll per wishlist for stores with wishlists <= 15
or
one click plus one scroll per item plus one click plus (at least) one scroll for stores with wish lists > 15
In other terms
one "all" click -> one page load, plus one page load for stores containing > 60 items, plus one page load for every subsequent 60 items.
versus
one page load per wishlist, plus one page load for stores containing > 60 items per wishlist, plus one page load for every subsequent 60 items.
So if one store has 16 wishlists, that's 15 additional page loads.
Again, I don't know what the answer is, but my time and effort have just gone up considerably. And, yeah, what's the better user experience? Waiting an extra second or two for a page load or having to load 16 pages? À chaque son goût.
I know different strokes for different folks, but if I have to work twice as hard to complete an order, then orders are going to happen half as often.
Also, apologies in advance if I didn't get all the click and scroll count exactly right, but I ought to be in the general ballpark for someone working on a standard laptop size screen.