Since quite a long time, MediaPortal comes with "MPI", the MediaPortal Extensions Installer.

This tool was created with the goal to make the installation process for our users as easy as possible.
In example, it allows to browse a list of plugins and skins located on our webpage, and install it directly from the application.

So we expected that MPI would be used by community plugin developers and skinners.
But sadly, it is not. Instead we see that community plugins and skins come with their own exe installers.
Dont get me wrong, we really appreciate the work of our skinners and plugin devs, but in terms of useability for our end-users, the current situation is very bad.
So what we want, is that MPI becomes the only way to distribute and install Community Skins and Plugins, hosted exclusively on the team-mediaportal.com homepage.
I guess that some people now have a puls of 220, but think about our users.
What we want, is an easy and uniform way for our users to find and install community skins and plugins.
And the solution is MPI.
Now, we know that MPI must have some limitations and downsides which lead to the current situation of not using it.
So, we want to improove MPI in the upcoming MediaPortal releases 1.0.1 and 1.0.2.
We would be very happy to hear from our community plugin developers and skin designers, what they miss in MPI.
Let us know!

*Update*
For quite many of the wanted features we need a skilled and dedicated Webdeveloper who is willing to work on the opensource repository we are using on the homepage.
Please get in contact with me if you want to do that.


This tool was created with the goal to make the installation process for our users as easy as possible.
In example, it allows to browse a list of plugins and skins located on our webpage, and install it directly from the application.

So we expected that MPI would be used by community plugin developers and skinners.
But sadly, it is not. Instead we see that community plugins and skins come with their own exe installers.
Dont get me wrong, we really appreciate the work of our skinners and plugin devs, but in terms of useability for our end-users, the current situation is very bad.
So what we want, is that MPI becomes the only way to distribute and install Community Skins and Plugins, hosted exclusively on the team-mediaportal.com homepage.
I guess that some people now have a puls of 220, but think about our users.
What we want, is an easy and uniform way for our users to find and install community skins and plugins.
And the solution is MPI.
Now, we know that MPI must have some limitations and downsides which lead to the current situation of not using it.
So, we want to improove MPI in the upcoming MediaPortal releases 1.0.1 and 1.0.2.
We would be very happy to hear from our community plugin developers and skin designers, what they miss in MPI.
Let us know!
*Update*
For quite many of the wanted features we need a skilled and dedicated Webdeveloper who is willing to work on the opensource repository we are using on the homepage.
Please get in contact with me if you want to do that.