The tiles concept is cool, but underutilized. They could probably expand on it to make it much more useful.
The arrival of highly-popular apps may potentially be a thing that is hurting Live Tiles. I mean that a firm trying to protect its existing branding or app look and feel is going to prioritize cross-platform uniformity over doing platform-specific features like Live Tiles for Windows Phone. There's no way to carry such an idea back to an iOS and Android app. I'm not sure how to address this so that developers exploit the platform more.
Our DrexelOne app has a very small target audience (our students, faculty, and staff). Because our web portal had no real "brand" when the mobile project started, we set about app development with only one major goal in mind: make the apps look native on each platform and exploit the platforms as best we could. As a consequence, the Android, BlackBerry, iOS, webOS, and Windows Phone apps all look different, but they each work just as their users expect because they work just like the built-in apps do. (The BB and webOS versions of our app are now withdrawn.)
Had we been protecting an established "DrexelOne" brand, we'd have approached development differently. I wouldn't necessarily be using pivots or panoramas in my app since such controls don't exist outside of WP. We probably wouldn't have a Live Tile since iOS and Android icons don't change. We certainly wouldn't support secondary tiles because there no concept of an "app bookmark" in the other platforms.
What will be important as we go forward as a community of users will be holding companies to a decent standard. Just as Android users can (and do) object when they're given an app that's obviously a port of an iOS UI, Windows Phones users are going to have to make it known which apps exploit the platform and which are "generic" in nature. This doesn't mean giving apps 1-star ratings for skipping one feature, but it may mean withholding some stars when developers ignore the capabilities that draw us to Windows Phone, and it
must mean writing a review to go with the rating and explaining in the review why the app isn't a "good" or "great" one on Windows Phone. (Maybe we can make "fit for iOS only" an acceptable put-down phrase.)