Jump to content

Emby Blog

  • entries
    550
  • comments
    4834
  • views
    3421804

Contributors to this blog

  • Luke 343
  • ebr 68
  • Carlo 31
  • 7illusions 15
  • ScottIsAFool 12
  • sross44 11
  • Abobader 11
  • radeon 8
  • xnappo 8
  • darwindeeds 7
  • Redshirt 6
  • Cheesegeezer 5
  • leedavies 3
  • Aphid 3
  • bigjohn 3
  • snazy2000 3
  • techywarrior 3
  • Soultaker 2
  • chef 2
  • gcw07 2
  • softworkz 2
  • marcelveldt 1
  • hurricanehrndz 1

EMBY Q&A Answers Part Two


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. 

  • Like 13
  • Facepalm 1
  • Agree 3

1 Comment


Recommended Comments

revengineer

Posted

You guys are doing great. For me, Emby has been working great and with very very very few issues for several years. From that perspective, the current release cadence with a sufficiently long QA period seems to work well. Be wary of growing the team; more coders require more revenue and that may require bigger adjustments to the business model than discussed elsewhere in the forum.

 

  • Like 4
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...