ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > Living Room

Matchstick - A streaming stick using Firefox OS [Kickstarter]

<< < (2/7) > >>

4wd:
I went for Ad-hoc because you could always switch it to that and send it a local file.  It seemed nicer for when you're on holiday, etc ... no wifi network required to use it.

Though you could always carry a cheap wifi router with you ... gadget bag gets heavier every trip  :-\

4wd:
SDK has been released: Matchstick SDK

Deozaan:
SDK has been released: Matchstick SDK
-4wd (November 26, 2014, 05:40 PM)
--- End quote ---

I came here to post that before I realized there was an update in this thread. (c:

4wd:
Matchstick has been delayed while they look at upgrading hardware/software, now possible August 2015 shipping date

I was hoping to get to play with it soon ... oh well.  :-\

The longer versionHello Matchstick Fans!

We’ll cut to the chase; Matchstick is not going to ship in February.

It’s been a very busy couple of months and we’ve had to make some hard decisions about how to move forward. We’ve decided to release the product when it is ready, and anticipate that to be in August 2015. Let us explain more.

Matchstick is, at its core, a group effort to bring a solid, open, and affordable alternative to the world of video streaming. Manufacturing is hard, but the totality of what makes a product experience complete includes so much more. That collaborative effort includes the hardware, the software, the content providers, and of course, the independent developers that will build on the Matchstick platform.

Hardware: We want to update the hardware. We’ve been looking at a number of exciting applications and potential experiences for Matchstick and we’ve determined we need to give it as much power as possible. So we’ve been looking to increase the CPU power from a dual core to a quad core chip. We’ve also been looking into common issues with Wi-Fi performance. Because of the location of most HMDI ports on HDTVs, many similar products have Wi-Fi connectivity issues. We’ve spent some considerable time reviewing ways to improve the antenna to ensure a consistent connection that some of the applications will require. We’ll keep you posted of course on the newest stats and specifics! Finally, we are eating the cost to improve the hardware, and passing along the benefits of improved hardware to our backers. It’s a cost we are willingly paying for the promise of a better product.

Software: With a new processor, we have some new opportunities. Matchstick, with Firefox OS inside, is being updated to support DRM (Digital Rights Management) capability. As you know, many premium content providers such as Netflix require DRM support. Matchstick has undertaken the mission to develop DRM as an independent project with the open source community. In fact, we’d love for you to get involved! If you’re a developer specializing in EME, MSE, and CDM technologies, we’d love to hear from you. We plan to use the Microsoft PlayReady technology and are excited to bring premium content to Matchstick. We’ll keep you updated as we work to contribute newly developed source codes for DRM back to the open community. It’s our goal to make sure open source technology doesn’t mean 2nd tier content and experiences!

Content Providers: We are continually in talks with all the content you will want to experience on your Matchstick. DRM is a barrier and has become our primary focus, and as we work to nail that down we continue to explore new opportunities to upgrade the entire Matchstick experience. We have been looking at some very exciting possibilities! We can’t wait to show you in the coming months.

Independent developers: We’ve seen some incredible possible use cases for Matchstick and want to make sure the developer community’s creativity is not hindered by hardware or software limitations. We feel strongly about supporting developers with something much more than a hacked Chromecast type device. The updates to Matchstick will ensure that.

CWuestefeld:
I understand delays, and I always thought their February promise was optimistic. But it really sucks that they'd wait until three weeks before it's promised in our hands to announce a 6-month delay. With a delay of this scope, it had to be something they've known about for quite a while; why wait so long to tell those of us who financed the project from the start?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version