For reference, the iOS SDK (in case you decide to create a small application that plays the quicktime video), can only read stuff that is:
- Inside the Application’s bundle
- the “temp” application’s user’s document directory (not shared between apps)
- Use the APIs to read the user video/audio library.
Number 1 and 2 would require that you create an iOS app that includes the video as a resource (which will -depending upon the video’s size-, make it a huge app)
Also creating an APP and deploying it, requires an Enterprise Licensing from Apple (so you can deploy to your company iP/ads/ods/hones). So I don’t think thats a good (and cheap) idea.
Using option number three you could go with VLC or something but they would have to pick the video from a library.
what would I do?
I’d set up a wi-fi network, with a local webserver that hosts the page. Then create a webclip on the iPads. All hardcoded. The WebClip could point to a real webpage, but a DNS “forging” inside your closed network could point it locally while they are there. This way, when they leave, if they take the iPads with them, the link will continue to work when they regain internet, as the DNS will be correct and point to the “external” website.
If the network is “closed” you can set it up in advance. A good 11n router should handle that.
No syncing, no weird app, no need to tamper each individual’s ipods…
Any catches?
Best Answer
The fullscreen YouTube uses of its website, is not a "real fullscreen" feature. It just maximize the size of the video to the size of the webcontent.
So unlike Vimeo (for example) you won't get a real fullscreen without YouTube updating it's webplayer (or you using the YouTube app) .