Leaderboard

Here is the next round of answers from our Emby Q&A session. The feedback from our previous blog post was exciting to see from all of you, and we are excited to share even more answers. The next round of questions and answers will be released next week as well! 1) What are some of the future goals of Emby? Emby wants to continue to grow and be the best media server option available for our users. We hope to move to a quicker release schedule than in previous iterations that is both more efficient from a development standpoint and exciting for our users. We love what we do here at Emby and we want our users and potential users to see that! 2) Would the Emby team ever consider moniterary "bounties" to help offset the development cost. We have actually seen this question a lot lately. We do not believe that this is the best way to decide what goes into development for a few reasons. First and foremost, we do not want people who have more money than others to decide what goes into production while others who may not be able to afford to donate or contribute go unheard. 3) How does the Emby team decide on what's next for Emby? The answer to this is deeper than most people probably think. Feature requests is one place that we look at to form our roadmap of future goals. Sometimes it's as simple as user feedback that something is not working as intended or could be implemented in an easier way to use etc. Other times our development staff has ideas based on industry trends as well as their own experience that they believe should be implemented. We take all of that and as a team decide what should be added and when. 4) In what areas can Emby improve? We as a team are always seeking to improve. We fully acknowledge that as a small company we are sometimes stretched "thin" but we do our best to always be both proactive and reactive with all of you. As mentioned above we hope to move to a quicker release schedule with a more agile methodology that allows us do so. We think we do a pretty great job at communication with everyone here on the forums, but we continue to strive to be even better here as well. Being able to give more flushed out answers and as much information as we can. Our goal is to always continue improving.

Thank you to everyone who took the time to ask the Emby team questions across all of the different platforms including here on the forums. There were a lot of great questions that were thrown our way and we've been excited to get the answers out to you. While some of the questions we were not able to answer, we did our best to give you the most accurate and clear answers possible. Now without further ado, here is the first series of questions and answers for you to look over! Please keep in mind more questions and answers will be coming in additional blog posts in the coming days, so not all questions are being answered today. Who owns Emby? Emby LLC owns the Emby product and is a private entity. The owners are undisclosed but note that the development team has full control over the direction of the product. We are not beholden to or under the influence of any investor or investment group. What is the history of Emby? Emby grew out of an open source project called MediaBrowser. Emby's origin in concept came out of that project but there is actually none of that code base still within it. Emby ended up being completely built from the ground up to be a server-based ecosystem as opposed to just a single app as the old MediaBrowser was. Around 2011 what is now the core development team for Emby were contributors to MediaBrowser. We saw the opportunity to build something more flexible than the WMC environment would allow and embarked on creating what we then called MB 3. The core developers spent over a year furiously writing code before anything was released to the public. It was then probably another two years of dedicated development before anything was truly usable as a system. In 2015 it was decided that we had moved so far away from what MB originally was that we needed a new name. A few of the devs got together and came up with "Emby". There are a few reasons behind that name but one of the main ones was that you needed something that wasn't already trademarked and domained. Emby fit that bill and has the benefit of sounding like "MB" when you say it. With the new name, we needed a new logo and we actually held a contest in the forum taking contributions from users and that finally landed us on the logo you see now. Since 2015 we have expanded the team and worked diligently to try and continue to craft the best truly personal media server system we can. We still have a long way to go but have also come a long way to where we are. What are the most popular Emby clients? We do not have exact data on this, due to sideloading and the such, but through the app store platforms we can gain general ideas. Android is the most popular amongst our userbase (both mobile and TV) with iOS in second place as the most downloaded app. What Emby clients do the development team use most for personal use? Our development team uses a wide variety of apps just as our user base does. We have people on the team using Android on mobile and TV, iOS, Apple TV, Roku and Xbox as well. As you can see our dev team really is as diverse as our user base when it comes to how we use the server. These were just a few of the questions about Emby as a product and who we are. In the next blog post we will be covering a few different things such as some of the future goals of Emby as well as release schedules and more!