No matter what you have to support both www and the straight domain, because different users will try different methods to get to your site and you don't want t

No matter what you have to support both www and the straight domain, because different users will try different methods to get to your site and you don't want to lose traffic. Because you have to set up both no matter what, I don't see any reason why supporting WWW as the canonical domain for webpages is going to add any complications, and as I explained above it solves a ton. In addition, the SSL stuff is irrelevant. You can use "www" under a wildcard cert just as easily as you can "app" or "dashboard", and if you're doing it right you're going to need to setup SSL on both anyways. Why does choosing WWW make it more complicated, and how will a "www" certificate get in the way?