I've used it for a couple months an absolutely love it. It basically replaces all of the "extra" features of View, other than the actual broker. You create your OS image, your application layers, and your templates, all within the Unidesk admin console, then spin them up from there. The integration between Unidesk and View is basically just a PowerCLI command to add the newly-created machine into the View pool. All VMware ends up seeing is a manually-built machine with the View Agent.
This takes the idea of app deployment (Mirage, SCCM, ThinApp, App-V, or however you do it) that either doesn't work or takes a PhD to configure and tosses them out the window. Unidesk also replaces the Composer pieces, as it holds the image itself. I use View only for the broker and security server at this point.
The added awesome benefit of it is how the layers are all stacked upon each other to form the PCs. Every layer is basically a VMDK file, and they're all mounted read-only (non-persistent, I think in VMware terms). The only files mounted persistent is "user personalization layer", which breaks into a user part and an app config part. So if your normal VDI machine has, say, 8 Gigs of Windows, 2 Gigs for user settings, and 10 Gigs of applications stored on it, you are looking at 20 GB per machine. If you have 100 of these, normally you'd expect to need 100 * 20 GB of storage. Since Unidesk utilizes the shared VMDK files for apps and the OS, you're looking at only 100 * 2 + 18 GB for the whole environment. Tell your SAN admin that she needs to buy you a cup of coffee or something....I keep telling ours that but I'm still forced to bring my Folgers from home.
All told, I really love the solution. Better yet, IT WORKS. I had it fully running in a matter of a week in my environment, and that's including layering all the apps myself. I'm early in my VDI rollout, but I've had nothing but positive reactions from my users, and my storage admin didn't have to bite my head off, either. Maybe she's into tea......