@Taylor and I were discussing how to manage the module library in Audulus 4. We’d love some feedback on these ideas:
Include Unedited User Modules
The way I approached the module library when creating it and adding modules to it was to have a unifying design principle so that modules look similar and have predictably labeled controls and I/O. The idea is that once people learn what individual icons mean, they can apply those to any module. The inputs and outputs are all at the top of the module except in certain cases like envelope inputs on filters or VCAs, etc.
There are lots of little design rules I follow to do this including spacing of UI elements and naming modules, all of which are pretty onerous to spell out and expect users to follow if they want their modules included in the library.
The solution to this was for me to just rearrange modules and add them as I had time, but as the community and number of modules grows, this task has become too large.
This would make it easy to continuously update Audulus without requiring a lot of extra work from me.
With the added tooltip help function described in this thread, it would also obviate the need to have to merge and edit module descriptions on the website.
The overall “help” function that pops up when you select a module could also direct people to the module’s entry in the forum.
Proposal
Instead of mixing the default Audulus library with user modules, we have a separate user-created library that includes the unedited versions.
There would still be an official library, but it would be pared down to really easy to use high quality modules that would be more inviting to new users and have a standardized UI created by a professional graphic designer.
This way we get the best of both worlds in the released version: A slick, uniform default library alongside an eclectic user-created module library that shows off all the variation you can have in creating a module.
Feedback
Would it be best to organize it by user then module type, or have just one big user library by module type and mix individual users together? I lean more towards highlighting the users’ forum names, like @RobertSyrett’s collection vs. @Stschoen’s. It would add to menu tree complexity, but with the iOS search function and eventual computer search function for modules, it might be just as easy to type in “VCA” and get every VCA module.
I lean towards highlighting individual users as this showcases their work in a nice way and presents their library of created modules as an individual offering rather than mixing them all together.
What do you think? Any and all ideas for this are welcome!