You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We just hosted our first event for which we used Hi.Events for ticketing! It went great, but we did get some customer feedback that the checkout UI was "a little confusing":
They thought it was strange that the checkout process didn't show the total at all during the process. I showed them that there is a cart button and clicking that would show the entire cart with the total.
After showing them that, they claimed that the button for showing the cart wasn't clear enough / obvious enough
Describe the solution you'd like
So I have two takeaways / suggestions here:
On mobile, either somewhere at the top or the bottom of the viewport, we should display the total that will be charged, without having to go into the cart to see it; it should always be visible. The screenshot below shows my suggested locations, in yellow and blue.
For cart clarity, I have two suggestions:
Add the word "Cart" after the cart icon on the "show cart" button.
Scrap the cart button as-is, implement the always-visible checkout total as a line above the 'Continue' button (in blue below), and just above that, in the center, is an arrow that when clicked, slides up to show the entire cart. Since it's right above the always-visible total, people would intuit that it is the cart button.
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. I agree the total should be displayed somewhere on mobile. I'd lean toward having the total on the bottom. Let me have a think about this.
Is your feature request related to a problem? Please describe.
We just hosted our first event for which we used Hi.Events for ticketing! It went great, but we did get some customer feedback that the checkout UI was "a little confusing":
Describe the solution you'd like
So I have two takeaways / suggestions here:
The text was updated successfully, but these errors were encountered: