New answers tagged

0

I saw this exact same problem in some concepts I was putting together. Commonly interactive cards are interpreted as containers if they appear to have a lower level of interactivity than the card itself. I proposed two solutions to this: Remove CTAs from the cards, and provide affordances to indicate the card is clickable. Such as hover/depression effects ...


0

Another way of handling this is to add a click target on the card someplace (an icon in the upper corner maybe), but leave the card itself clickable. New users will probably go directly for the icon and it will launch the card click, and veteran users might discover that the entire card itself is clickable. I don't see a reason to remove the card's ...


4

You have nested actions: a clickable card with a clickable button on it. Your testing has shown that users did not understand that. Instead of having the card clickable you should provide a second action and do not make the card itself clickable at all. In this case you can distinguish the importance of the actions by designing a primary and secondary action ...


0

If you try look at your cards as a user with no prior knowledge of your system, what would you think being the primary action of the card? Probably your users thought as I did. What I see as the primary action of the card is the button "Add to bag" the date being secondary action. If the date is a button at all? If you look at the secondary actions ...


Top 50 recent answers are included