3 ms·
The problem is that it makes for a crap product roll-out. If you remember the Chromecast announcement, the SDK was presented as coming imminently. It really wa
by bane 13y ago
The problem is that it makes for a crap product roll-out. If you remember the Chromecast announcement, the SDK was presented as coming imminently.
It really wasn't cool when they selected preferred providers to be the only ones allowed to release anything built with the SDK. This weird limbo period really pissed lots of early buyers off.
>the usual reason is that Google doesn't want people building apps on unstable APIs
But they let lots of preferred groups build apps. Very complex ones, not just the the simple "put my photos on my TV" apps even. The SDK has obviously been in good shape for months.
AND THEN they simply broke their initial Netflix promise because it was simply too popular.
It was clear from some of the early experiments with the SDK that it was "good" enough for many early apps. And if later improvements showed up, then that's great.
Back before December, they made another announcement that made it sound like it was going to be out any day. And then it slipped and slipped some more. Just release it and say it's beta. After all it's Google and most of the stuff they ship is barely better than a beta anyway.