We are considering unity WebGL to be the client for a 3D site. Think of it as a shopping site with transaction and cart. The customer can walk into the supermarket and buy everything. It has to support financial transactions including bank accounts.
Is it possible in unity? Is it advisible to use unity as the client?
EDIT: I tested a scene with one plane, a camera and a directional light. After taking advices to reduce build size, the output became 5.7MB. Is this the absolute minimum we can get? No way to reduce that further with the cost of CPU maybe?
Do you suggest any strategy to make the initial loading less nerve racking? Let’s say we show a login dialog and place it on index.html to make user fill the form. This will give us a little time. Then what? Is it possible to load unity’s .js files with multiple connections say 8 simultaneous connections to boost initial load time?
This is a terrible idea. WebGL isn’t mature enough for this in general and Unity’s WebGL implementation still leaves much to be desired. Just make a normal website.
I agree completely about the webgl and webplayer. But it is supposed to be a different “thingy” not like just any other site. I think it takes a few month to implement it. Maybe (just maybe) that could relax the WebGL’s immature status. Do you think it is a good bet?
You mean a normal unity project that interacts with some facade and that facade interacts with the server?
Yes. Its simple to move data between the two ( http://docs.unity3d.com/Manual/UnityWebPlayerandbrowsercommunication.html ) and ideally you could keep any sensitive information away from Unity (personally I’d be a lot more comfortable with transaction data moving through well understood channels).
Also means you can fall back gracefully to a standard site which might be a nice to have. Don’t want to turn business away because someone is on an older browser or the like.
These days you may be able to get away with it. Seems like it’d be little in difference from all of the Flash websites that were a rage before the news of depracation.
Maybe make some kind of template system where you have content areas and the data is pulled from text files and displayed.
But really if you’re using Unity might as well go all out. Make navigation work by literally exploring the site moving character forward in a screen down a hall or whatever. Doors with signs above them are the links.
You could make a flash-esque site with this approach. But flash sites went out of vogue quite a while ago. These days data-driven design is farm more common, and far more accessible to the average web developer. Unity would be fine for some snazzy animations and graphics, but it wouldn’t exactly be optimal for a more complex, data-driven interface. Possible, but not the most elegant solution, and probably more trouble than it’s worth.
A data-driven CMS with embedded Unity examples would probably be a better approach for a more long-term regularly updated website.
36 MB for an empty scene?!! That’s insane. The WebPlayer target always produced builds that were a fraction of the desktop build size. This new WebGL target appears to have scaled up size by many factors.
