| At the Guardian we needed our own video player, because we couldn't rely on a third party platform not to take down something that we published. Editorial independence was important. We implemented our player on top of video.js, and most of the developers who were there at the time still have nightmares about it. We finally got the thing working, looking good, embeddable, reasonably cross-browser. We shipped it. A few days later, we get a curious email from some ad provider. "It looks like your VPAID ads have stopped running!" Oops. We'd naively believed we could live without Flash (I take full responsibility for this stupidity). The sales folks pointed to a big gap between our old projected revenue and our new projected revenue. So we went and did the work[0], hating every minute of it. The underinvestment in ad-tech by publishers and the cancerous ecosystem of vendors that have grown up around it is one of biggest collective mistakes made by an industry. I am optimistic that this problem can be solved, and we are actively looking at this at my current employer. We sell direct, usually without a ton of intermediaries. Talk to me if you want to know more. Incidentally, if you want to know if a publisher is going to survive the next five years, a decent proxy is the number of intermediaries involved in their ad supply chain. [0] https://github.com/guardian/video-js-vpaid |
I did plenty unpleasant work for them, like building a clean redesign, agonizing over page load speeds, and then filling up the page with multi-megabyte tracking tools and every possible ad under sun (which would not only ruin the design, but often inexplicably and randomly break the page because of really, really shitty code).
All that work was pleasant compared to the horror of working on the video player though, and I felt bad for the full-timers who were usually put on 'bug-fixing' duty while we contractors got to work on the cool projects...