Overview of MB clients

[steve1977 67]

I understand that one single MB Server exists. Can you shed some light into the existing and planned MB clients. I assume that MB Classic will no longer be developed and this can focus on MBT?

Is it fair to differentiate between three types of clients (HTPC, mobile, plugins)?

 

1) HTPC (branded MBT on website)

* WIndows 7/8 (currently in alpha phase)

* RPi (planned, looking for developers)

* Linux (planned, looking for developers)

* OSX (no plans yet?)

* Google TV (no plans yet?)

* ATV (no plans yet?)

 

2) Mobile

* IOS iphone

* Android

* Windows Phone / RT

* IOS ipad (under development)

 

3) Plugins

* Mediaportal

* XBMC (planned, looking for developers)

 

 

Is that list and structure accurate?

[Redshirt 1487]

It's close. The XBMC saver plugin will allow MB server to act as the back-end for an XBMC client. OSX I'd categorize as looking for developers. The server API is rich enough that absolutely any device that can communicate over HTTP and has a public api can consume it. Regarding Google TV, or should I say Android TV... I'd like to port my Android app over to it. There are a few layouts that would need to be improved to avoid excessive horizontal navigation. Live and learn.

[gcw07 347]

There is also the Roku, which is currently in beta. Apple TV is something that we can't do anything about until Apple decides to open up there SDK for it. At the moment you can't develop apps for Apple TV unless the ATV device has been jail broken.

[Redshirt 1487]

I didn't even notice Roku was missing from the list. /Me hangs head in shame.

[Luke 37232]

You can learn more about Emby apps on our website:

 

https://emby.media/download.html

 

Enjoy.