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

Key to adopt open source product

Friends, I am working on business solution implementation on open source product called Kaltura. Kaltura is a media management solution and has loads of features that compel any business to take a peek into it. More-over this is the only complete end-to-end open source software available to handle digital assets. But it comes with its own head ache. Considering its open source, its understandable. I feel, handling these would ensure you the success in your open source product implementation. 1. In my opinion, before adopting any open source software, build the capability to deal with the inconsistency bundled in the open source software. 2. I would avoid involving external consultants for 2 reasons.      a. I am not sure, they would bring necessary expertise on to table      b. I fear that there would be little ownership, they will not see big picture of my business (neither I am interested to share it all) 3. Alternative to that is to build the team that is capable of debuggin
1 comment
Read more

Secure your application on cloud

Handling sensitive data Define sensitive data for your application. Classify as sensitive data and confidential data. Sensitive data is something like password, credit card account number, something that you should not compromise at all. Confidential data could be your customer’s health record, something that requires your permission before its usage. So, you need to define sensitive data in the context of your application. There are many ways to protect the sensitive data in transit; the easiest way is to use SSL. This is nothing different than handling sensitive data in any traditional application.   However, make sure you apply this rule while designing your application for cloud deployment. Alternatively, you can encrypt the sensitive data and transport. Be noted that any kind of protection you design, will have implications on performance. However this is ignorable considering the nature of sensitive data. If you just want to protect your data from being tampered during
Post a Comment
Read more

Sub-netting: Divide a network into 2 or more networks

Points to keep in mind: 1. Computers that belong to a subnet are addressed with an identical most-sig bit group in the IP addresses 2. IP is logically divided into NetworkIdentifier/Routingprefix and Restfield/HostIdentifier 3. Routing prefix can be expressed as CIDR (Classless Inter-Domain Routing) notation. Ex. 198.51.100.0/24 Implies NetworkIdentifier has 24 bits allocated and Rest field has 8 bits allocated 4. A network is characterized by subnet mask or netmask, applied by bitwise AND operation Ex. For 198.51.100.0/24, the subnet mask is 255.255.255.0 Subnet masks are used to identify the networks *If 198.51.100.0 is NetworkIdentifier, then 198.51.100.255 is BroadcastIdentifier For Class A, mask is 255.0.0.0; Class B, mask is 255.255.0.0; Class C, mask is 255.255.255.0 5. Traffic is exchanged between subnets through routers, when the routing prefixes of the source and destination addresses differ; A router serves as a logical boundary between the subnets. Advantag
Post a Comment
Read more