> using data from sites like StubHub, Vivid Seats, SeatGeek, etc
Congrats! That is inspiring you kept the passion for this for over 14 years. I’m assuming your data needs changed over this timespan so how did you end up getting this data? APIs, scraping, something else?
Appreciate it. A lot of challenges, one of the most difficult that sticks out was building out the ability for users to track prices on a custom zone that they define (Sections 101+102, rows 1-4), and making it so that the price trend for this zone would show up retroactively (back to when the event went onsale), not just to "start tracking" prices in that zone once the user created it. There's a lot of cleaning of data that goes on for this, since different sellers might use slightly different section names for the same section, to ensure that you're including all the ticket listings that you should be.
Thanks! It’s definitely something a few people have mentioned, for now I’m keeping the focus on the public site and the experience there. I want to prove that it's viable as a consumer-facing product.
> using data from sites like StubHub, Vivid Seats, SeatGeek, etc
Congrats! That is inspiring you kept the passion for this for over 14 years. I’m assuming your data needs changed over this timespan so how did you end up getting this data? APIs, scraping, something else?
Great job. The UI is clean and easy to use.
What were your biggest challenges while working on this?
Appreciate it. A lot of challenges, one of the most difficult that sticks out was building out the ability for users to track prices on a custom zone that they define (Sections 101+102, rows 1-4), and making it so that the price trend for this zone would show up retroactively (back to when the event went onsale), not just to "start tracking" prices in that zone once the user created it. There's a lot of cleaning of data that goes on for this, since different sellers might use slightly different section names for the same section, to ensure that you're including all the ticket listings that you should be.
Nice! You should consider offering an API.
Thanks! It’s definitely something a few people have mentioned, for now I’m keeping the focus on the public site and the experience there. I want to prove that it's viable as a consumer-facing product.