Okay, so we just launched our new news pages that support video (ex: http://www.pittstate.edu/press-media/detail.dot?id=241226
). Pretty happy with it all around, and it supports any video hosted locally, or remotely if it's based on oEmbed. There is also a video portal in the works as well. This has been a big step for PR, and a not insignificant commitment by them to start producing video to begin with.
The news page is a BIG improvement over our old ones, but naturally the first thing I hear this morning is a complaint: "Why doesn't it support iPhones?" We are using Flowplayer, which is Flash based... so you can do the math there.
So, I'm wondering what other folks are doing. If I support mobile video, I don't want to JUST support iPhone, because Android is nearly as big on campus. I'd much rather support *mobile video,* not just iPhone. I know YouTube and Vimeo have HTML5 support, but that also adds an extra step to PR's workflow that I can already see them not accounting for ("We need to put out this press release now, but the video needs an hour to process! What do we do?"), and of course you can't brand the third party players.
On the other hand, doing it ourselves means maintaining two players (or using VideoJS
, which seems to be the only halfway happy solution ATM) and having to encode 4 video streams (FLV, OGG, h.264, WebM) if we want to make sure to support everything. Up until now, I've been pretty deadset that I didn't want to work with HTML5 video until they standardize on a single codec, but that's not a good excuse with UX is concerned. If the people demand it, the people will likely get it.
I'm curious what you are doing. Did you just bite the bullet to rely on a third party? Do you have the means to do it all yourself? Are you ignoring the issue for now? Are you just supporting a single device?