I’ve been scouring the forums for a comparison of the web player and the stand-alone application. Anyone have information they can share, or a link to a good pros-and-cons article?
For example: with a downloadable app, we’ll need to be able to automatically update it with improvements and additions. How tricky is that?
I’d say in that case, go with the web player. It’s perfect for stuff like that, as all clients get the updated version at all times (no need to push updates on people, which can be a hassle, even if automated). Requires internet connection, though.
For standalone apps and automatic updating, AssetBundles may be of interest to you. Never used them myself, but I guess this might be one of their uses.
Edit: BTW - there should be no “real” difference between a web-player and a downloaded application (both can run in fullscreen and both are run client-side).
Thanks ToreTank! I’d really like to see a comparison of the two approaches though. Can’t believe it’s so hard to find. I (and my boss) would still like to see that if anyone reading this has info!
Hey ToreTank, one more thing: where did you find out that both are full screen and both run client side? I’m just looking for some documentation on these!
The applications run client-side using the web player plugin which is quickly installed the first time you hit a web-deployed application online (much like any flash application - have you tried the online demos from unity3d.com?). Even though the app is run client-side, you can still stream stuff on-demand from the web, so the download/startup times will not necessarily appear to be very long (for example, you only need to download the main menu before you launch the app, and you can start downloading other stuff while the user is busy reading text or navigating menus).
Just to clarify - both of them have the option to be full-screen, they don’t have to be.
Not really sure where you can find info about the different build targets and their capabilities, but you might want to check this out: http://unity3d.com/support/documentation/Manual/Publishing%20Builds.html