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
Thanks, team, for quickly solving the ticketing UX issue. But it still needs some work.
The current UX makes it almost impossible for newbies to register a ticket for WordCamps (15 steps before they see the checkout button - then 3 more steps to confirm payment). Had a word with several newbies. It won't just affect us but all the scheduled WordCamps - hindering the mission of bringing new people to the WordCamps.
Given that the biggest web community in the world is coming up with this UX getting new members is not recommended.
People are just not doing it. We at WordCamp Delhi sold a total of 3 tickets total in the last five days. (We were selling 10-15 per day before this)
I'd suggest creating an account and redirecting back to the ticketing page while the person gets an email to confirm their account in the backend.
It'll be efficient.
The text was updated successfully, but these errors were encountered:
Thanks, team, for quickly solving the ticketing UX issue. But it still needs some work.
The current UX makes it almost impossible for newbies to register a ticket for WordCamps (15 steps before they see the checkout button - then 3 more steps to confirm payment). Had a word with several newbies. It won't just affect us but all the scheduled WordCamps - hindering the mission of bringing new people to the WordCamps.
I've recorded the steps here -
https://scribehow.com/shared/Creating_an_Account_for_WordCamp_Delhi_2024__SmvphzvrTeuTWs2undaV_A
Given that the biggest web community in the world is coming up with this UX getting new members is not recommended.
People are just not doing it. We at WordCamp Delhi sold a total of 3 tickets total in the last five days. (We were selling 10-15 per day before this)
I'd suggest creating an account and redirecting back to the ticketing page while the person gets an email to confirm their account in the backend.
It'll be efficient.
The text was updated successfully, but these errors were encountered: