4 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Ananth Balasubramaniam commented  ·  January 28, 2012 21:07  ·  Flag as inappropriate  ·  Delete

  Alternate way: Let’s suppose the API allowed us to pass in the URI to a XAML file instead, one that wasn’t allowed to link to any assembly namespaces (so it couldn’t run custom code or require the OS to load in any other assemblies). The OS would load the XAML file from the given URI, verify that it didn’t require or link to any assemblies and set its content root into a “tile”, allowing the XAML to run any animation it needed. Any URI’s that referred to the application’s isolated storage would be redirected to access the appropriate location. Battery life concerns could be addressed by suspending ALL (and I mean ALL) live tile animations when battery saver is enabled. This would allow flexible, really live tiles that would be on par with OS live tiles.

  Read more about it here: http://ananthonline.net/2012/01/28/what-windows-phone-does-right-and-what-windows-phone-does-wrong-live-tiles-3/

• Fyter commented  ·  December 16, 2011 09:29  ·  Flag as inappropriate  ·  Delete

  System can do, App can do too.
  Like 'People' tile animation, like SMS's number, like picture tile animation.

• Alex F. commented  ·  October 12, 2011 00:38  ·  Flag as inappropriate  ·  Delete

  I think you confused WP7's live tiles with Android's widgets. No thanks.

• Ananth Balasubramaniam commented  ·  September 28, 2011 14:20  ·  Flag as inappropriate  ·  Delete

  Such live tiles can also interact with background agents by being passed in to OnInvoke via ScheduledTask.