The Early Years
In July of 2006, JMediaManager publicly released his personal AniDB client, AniDB Monitor giving AniDB members the ability to automatically hash their files for comparison, add them to their AniDB Mylist and allowed users to update their episode watched states with ease. Development on predecessor however halted shortly after AniDB Monitor’s initial release having reached the initial goals of the program. Development on AniDB Monitor would remain dormant until 2008 when a user on the MediaPortal forums announced they had begun working on an anime plugin simply known as My Anime. Demand for such a plugin to allow users to view and watch their anime collection was high and many users followed development on the plugin, however for unknown reasons the original developer abandoned the project to the dismay of many and once again the MediaPortal community was left without a suitable anime plugin. JMediaManager, who had also been following the development of the plugin announced he was going to develop his own plugin and using AniDB Monitor as a base was able to quickly produce a release. On February 13th, 2008 the MediaPortal plugin My Anime was released to the public, this also signified the start of what would later become the JMM Suite.
The plugin quickly become a very popular with requests and bugs coming in almost faster than JMediaManager could implement them. A lot of the requests and even some of the bugs reported were the result of the quick release and combination of various parts of AniDB Monitor. Development continued forward with various parts being updated or rewritten as time went on eventually leading to the release of My Anime 2 on June 2nd, 2009 containing a lot of improvements and additions over it’s predecessor. Like usual development continued on and as My Anime’s popularity continued to grow it slowly started to outgrow being just a MediaPortal plugin and the idea of My Anime becoming something more started to transition to reality.
The JMM Suite
As development continued on My Anime 2 and the plugin became more and more popular, it started becoming more of a collection manager instead of a content consumer. Additionally, the ability to have access to this collection outside of MediaPortal was becoming more requested as users wanted a database that didn’t rely on MediaPortal. It was also around this time that the project gained its first new members, Craige and MaxPiva who also wanted to see the project grow beyond a MediaPortal plugin. At the time, there was no centralized database so developing a plugin for another program or even a standalone program would require it’s own database. To avoid this and to allow any program or plugin access to the database, it was decided that all server functionality would be moved out of My Anime 3 and into it’s own program. However with the project now growing, a new name to encompass the current My Anime 2 plugin and the then unnamed server program was needed, the name Otaku Media Manager was selected and development on the standalone server program pressed forward.