Skip to main content

Point of view on TV Application Layer

With the internet everywhere, content aggregators, broadcasters, and content producers are compelled to find new delivery channels. SMART TV happens to be the next trend riding the wave. Ofcourse, we need to see how SMART TV concept catches up in India as there is cost barrier. 
SMART TVs are finding their ways in west, however, it remains to be seen whether they can double up as an effective delivery medium. In my view, the major concern is that, the user still has to switch to TV application from main screen to access. As a viewer, I don't find it convenient to navigate, every time I need to access TV app, rather I user my tablet to access app.

I wished, TV applications being displayed alongside main screen, more as a companion one and had access to the context of the content being broadcast. This is the tricky place to be in and I am not sure, it is going to be reality because of content protection policies. However, one thing is for sure, the broadcasters are sitting on golden mine.

Huge monetizing opportunity awaiting ... for both, content broadcasters, and TV app developer community.

Coming to SMART TVs, there is no standards for TV app and running the TV app on different manufacturer requires re-writing, re-compiling the code. Heavily discouraging for the developer community that develop TV app.

At Mindtree, we evaluated TV application layer, an open source framework from BBC attempting to provide abstraction layer with an intent of writing TV application once, and run them on any connected SMART TV.

Our evaluation article can be found here.

Comments

Post a Comment

Thanks for your comments.

Popular posts from this blog

GCP: GAE - Memcache best practices

Memcache is a distributed in-memory data cache in front of or in place of robust persistent storage for some tasks. GAE includes a memory cache service for this purpose. Best practices for using memcache: 1. Handling memcache API failures gracefully; Do not expose errors to the end users 2. Use batching capability of the API when possible 3. Distribute load across your memcache keyspace Use sharding and aggregating for improving performance efficiency. Use TTL (expiration policy) to make sure the memcache does not fill-up indefinitely Use getIdentifiable() and putIfUntouched() for managing the values that may get affected by concurrent updates Use batching (getMulti ("comments", "commented_by") ) to fetch related values together instead of one by one Use graceful error handling
Post a Comment
Read more

Innate and Non-innate learning

I am reading a book called 'What did you ask at school today?' by Kamala V Mukunda. Would like to share some learning. The book is intended for teachers as primary audience, nevertheless, good for any adult to gain deeper understanding on learning process. She talks about brain structure, innate and non-innate learning aspects and talks about synergy needed between the two in the first two chapters. Firstly, innate learning is something that would not need explicit training. For example, kids learning the language. They wont feel strained or stressed during this kind of learning, just because they enjoy the process, where as non-innate learning focuses more on class room learning. It is accepted that learning through playful means will have more impact on kids than the impact through the structured learning. A physcologist, David Geary puts it this way - while learning through playful means has more impact, children should be encouraged to learn the skills through structure...
Post a Comment
Read more

Essential GCP services for a new age application

Identity and resource management IAM  Identity aware proxy Resource Manager Stackdriver Monitoring Stackdriver Monitoring: Infrastructure and application monitoring Stackdriver Logging: Centralized logging Stackdriver Error Reporting: Application error reporting Stackdriver Trace: Application performance insights (latency) Stackdriver Debugger: Live production debugging Development management Cloud Deployment Manager: Templated Infrastructure deployment Cloud Console: Web based management console Cloud shell: Browser based terminal/CLI Development tools Cloud SDK: CLI for GCP Container registry: Private container registry Container builder: Build/Package container artifacts Cloud source repository: Hosted private git repository Database services Cloud SQL: Managed MySQL and PostgreSQL Cloud BigTable: HBase compatible non-relational DB Cloud Datastore: Horizontally scalable non-relational (ACID) Cloud Spanner: Horizontally scalable relation...
Post a Comment
Read more