I've been testing the Chromecast Google TV interface. There was a little hiccup when my new Chromecast device ran into some issues.
I'm using my older HD model, and it works fine. So, I've been using the Chromecast and so has a family member. She noticed something that was of concern. She said that the Chromecast was not as responsive. So, I decided to check it out.
Turns out that the device is as responsive as my Roku device, but the way the interface works makes it appear slower.
On Roku, if I launch, say, Peacock, the screen blanks and within 2-3 seconds, the Peacock splash screen displays. However, on Chromecast, when I launch Peacock, the screen remains on the menu, and within 2-3 seconds, the Peacock splash screen appears.
The difference is that Roku indicates that it accepted your button press by changing the screen. Even though it was to a black screen, it still was a change, and you knew that your button press did something.
With Chromecast, the menu doesn't change until the splash screen displayed. That means that for those 2-3 seconds, you had no indicator that it had accepted your button press. And, if it had indeed not accepted it, then those 2-3 seconds would have been the same.
Roku letting you know visually that your button press was accepted and that the device was doing something is a better experience than 2-3 seconds of no activity on the Chromecast. Chromecast could learn a thing from Roku about this.
The end result is that the Chromecast is as responsive as the Roku, it's just that it seems that it's not. That's a bad experience. My Streaming Life isn't as much fun if I'm not sure my streaming device is working.
No comments:
Post a Comment
Your comments are welcome. Abusive or off-topic comments will be removed.