I’m starting to get a clearer picture of how it will all tie together; but as I walk through the process in my head, I still have some questions on how this will work.
I’m thinking about this flow as an end user…
- I go to the library, I’m checking out some modules - maybe even thinking about buying something
- I find a plugin or module that looks interesting, I click on it to learn more
- There’s an info page that’s very lean on information about the module (how it works, etc.) - but it’s got a screen print so I can see it, and some tags so I know at a high level what it does
- There is also a link to the Plugin or Module website embedded in this page that will direct me to the manufacturer’s website where I can learn more about it - so I do that
- Now I’m somewhere else - where do I go to actually buy it? Will their site link me to a separate VCV storefront that I go back to?
I’m a process guy by profession (and nature honestly) so I can get hung up on thinking about the design and process flow of things, hence the questions. I’m also still not 100% how the store ties in, so maybe I’m just not getting that piece just yet and this is all accounted for in your plan already and I’m just wasting some keyboard strokes.
In my head, the most-convenient and efficient approach is a combined library/storefront. I browse for modules, I can add them to my rack just like the current site with the +Add button, or click on a page, get a basic product description, and add to cart right there to purchase. So the library is the storefront, and if developers want to maintain a separate site with more details/marketing/manuals/etc they can. Individual modules appear, and if part of a larger plugin/bundle, then clicking on the details takes me to a product page for the plugin.
If I can’t purchase from the Library and that’s not really it’s intent, then I could see people getting confused about why there’s this informational library for a product that I can’t actually go and make purchases from. Example: I don’t go to a public library to know which books exist and their topics, I go to a public library to read them or check them out for later reading. Hence the combined library/store-front assumption on my part.
And like any storefront, I still feel like there should be a product page with some basic copy. If I’m thinking about buying a module and I need to go to a different website for basic information about it, that’s going to throw me off. Do I buy it on this other site? If not, then where? Am I supposed to go back? Do the developers link back to the VCV store?
What I’m picturing isn’t really anything more than a “Product Description” type section on the library details for a given module, with an “Add to Rack” or “Add to Cart” button on the same page so everything’s self-contained. For more details, link to the Plugin/Module/Developer website (which you’re doing already), and maybe include a link to the manual if there is one. But this way, if I browse a cool module in the library, I can hopefully have enough information to decide if I want to add it to my Rack or buy it right there.
Regarding reviews: I may be an optimist, but I think your overall user-base will generate higher quality reviews than the iTunes user-base just due to the underlying complexity of the product. Good reviews (if achievable) would ideally help newbies and more experienced users alike explore modules. But particularly new users who may get overwhelmed by the number of options.
Anyway…sorry for another long post. Hopefully, my perspective adds some value. If you’ve already worked through this and I’m just not “seeing it” yet, that’s ok too. I look forward to what’s in store.