The most common deployment scenario for physical clients is local deployment. Most customers use deployment tools such as Microsoft SCCM or similar, and deploy the ThinApp packages as MSIs. You can very well stream to physical devices, but that is mostly used in special use cases. For example, you can choose streaming because of the in-place update mechanism it offers.
Choosing local deployment offers a couple of benefits. It fits seamlessly into the existing processes and the packages have more or less the same performance as a locally installed version of the application.
Where you decide to place your packages on your clients is an interesting discussion. I've seen enterprises creating a specific ThinApp folder on their clients where all ThinApps go. Another method is to deploy the packages into the default location, that is, C:\Program Files\ApplicationName (VMware ThinApp). My personal preference is to deploy packages to C:\Program Files...