I started writing Attendize about 11 years ago when I had very little professional experience. As a result, the code is quite terrible and difficult to customize and extend.
With Hi.Events, I designed the API first, making it more robust and open to extension. One of the most frequent requests for Attendize was for more flexible ticketing options, such as ticket tiers and donation tickets. I've incorporated these features into Hi.Events, along with much more powerful attendee management and customization features.
awesome. :) i should maybe mention that i organize https://ai.engineer, which used ti.to. tito worked well for us, very little complaints except that coupons were laborious to create and maybe it could have been easier to aggregate different stages of ticket between early bird/late bird/general admission for data analysis
With Hi.Events, I designed the API first, making it more robust and open to extension. One of the most frequent requests for Attendize was for more flexible ticketing options, such as ticket tiers and donation tickets. I've incorporated these features into Hi.Events, along with much more powerful attendee management and customization features.