Dear Yahoos,

I have a question regarding the example widgets included in the SDK and how incoming developers new to the Connected TV platform should interpret them… 

Should they be interpreted as working examples of “Best Practices” in terms of TV App implementation or just “Simple Mockups” that are not intended to be example of real word Apps?

Would the code in the example widgets pass the TV Widget QA process in a real world deployment?

For example do they represent the preferred handling of QA issues such as…

Disconnected Network Handling
Negative Inputs
Remote Debugging
Account Authentication
Media playback
Handle Image Load Failure
Http Requests
Asynchronous Calls
Etc?

At first blush, it looks like the majority of the above issues are touched on by at least one of the SDK example widgets.  Not sure if they were intended to be production quality.

Thanks!  :-)

<br>Any thoughts?...<br><br><div class="quote"><div class="quotetop">QUOTE<cite>(Daniel @ 27 Nov 2011 1:31 PM)</cite></div><blockquote class="quotemain">Dear Yahoos,<br><br>I have a question regarding the example widgets included in the SDK and how incoming developers new to the Connected TV platform should interpret them…&nbsp; <br><br>Should they be interpreted as working examples of “Best Practices” in terms of TV App implementation or just “Simple Mockups” that are not intended to be example of real word Apps? <br><br>Would the code in the example widgets pass the TV Widget QA process in a real world deployment?<br><br>For example do they represent the preferred handling of QA issues such as… <br><br>Disconnected Network Handling<br>Negative Inputs<br>Remote Debugging<br>Account Authentication<br>Media playback<br>Handle Image Load Failure<br>Http Requests<br>Asynchronous Calls<br>Etc?<br><br>At first blush, it looks like the majority of the above issues are touched on by at least one of the SDK example widgets.&nbsp; Not sure if they were intended to be production quality.<br><br>Thanks!&nbsp; :-)<br><br></blockquote></div>