Keypoints
- Multi-criteria ratings let customers score comfort, quality, size and more, instead of one vague star rating.
- Every rating is stored in your own WordPress database and shown with the widget template you choose.
Demo post: replace or delete it once real posts are published. What if settings are saved based on the breakpoint currently being viewed, with Web as the default breakpoint? This would allow us to manage responsive settings independently. For example, if a setting isn’t relevant to mobile, we can hide it when viewing the mobile breakpoint while keeping the same setting available on Web.
Why one star rating isn’t enough
What if settings are saved based on the breakpoint currently being viewed, with Web as the default breakpoint? This would allow us to manage responsive settings independently. For example, if a setting isn’t relevant to mobile, we can hide it when viewing the mobile breakpoint while keeping the same setting available on Web. This would also make the responsive behavior clearer and prevent users from configuring options that don’t apply to the selected breakpoint.
Choosing the criteria that matter
What if settings are saved based on the breakpoint currently being viewed, with Web as the default breakpoint? This would allow us to manage responsive settings independently. For example, if a setting isn’t relevant to mobile, we can hide it when viewing the mobile breakpoint while keeping the same setting available on Web. This would also make the responsive behavior clearer and prevent users from configuring options that don’t apply to the selected breakpoint.
Showing the breakdown on product pages
What if settings are saved based on the breakpoint currently being viewed, with Web as the default breakpoint? This would allow us to manage responsive settings independently. For example, if a setting isn’t relevant to mobile, we can hide it when viewing the mobile breakpoint while keeping the same setting available on Web. This would also make the responsive behavior clearer and prevent users from configuring options that don’t apply to the selected breakpoint.
Stars, emojis, thumbs or numbers
What if settings are saved based on the breakpoint currently being viewed, with Web as the default breakpoint? This would allow us to manage responsive settings independently. For example, if a setting isn’t relevant to mobile, we can hide it when viewing the mobile breakpoint while keeping the same setting available on Web. This would also make the responsive behavior clearer and prevent users from configuring options that don’t apply to the selected breakpoint.
-
The idea would be to switch between Web and Mobile breakpoints and have the available settings update accordingly. Settings changed under Web would remain specific to Web, while mobile-specific settings could be configured separately when switching to Mobile.
-
We got your point Mike!
-
What if the settings panel adapted based on the breakpoint the user is currently editing? Web would be the default, while Mobile could have its own responsive settings. This would allow us to hide irrelevant options on Mobile instead of displaying settings that have no effect at that breakpoint.
Leave a Reply