![]() Of course writing that manual may make it easier to see the app from a new users perspective, documenting workflow often makes you realise how inconsistent/convoluted it is. IMV starting on a simpler/more cohesive/discoverable ui for common tasks is going to add value to more people than a detailed manual. The context for my comment came from the competitive disadvantage thread which has numerous people commenting that relatively basic functionality is somewhat obscure from a ux perspective, documentation is hard to find and/or often out of date and the capabilities of the product are not easily discoverable. ![]() And if they don't, then, at least, my reply can be a two line "read this: LINK" rather than a big explanation, which shifts over time (and perhaps contains inaccuracies based on my state-of-mind at the time). But quite a few do as well (they post that they did when they have additional questions). Yes, it is true that many users will ask and not read it. Mostly I update the Wiki to save my own frustration. Oh, and even it has pretty substantial documentation. MC falls much more into the latter category than it does to things more akin to Apple's new Photos app (as an example). I've never seen a capable professional NLE, or DAW, or programming IDE, that doesn't need at least some documentation. But if you want it to remain a powerful professional application, you can't always do that. You can do that, if you're willing to neuter the application. Photoshop needs substantial documentation, but not because the UI should be simplified. But in each of those groups there are people who have fallen in love with the technology and turned away from the customer experience. ![]() I have great respect for the technical expertise of the people at JRiver, on the forum, and in this very thread. But when I've tried other software, if I have to go online to ask a basic question about getting the software to run, I'm more likely to go online and look for alternatives. And then links to the wiki and the forum. A quick start guide that explains simply the steps to playing audio, playing video, how to import (and why) and how to manage the library. It is a simple thing to write an introductory letter that SHIPS WITH THE SOFTWARE. For every one of those how many actually did give up trying? I believe there was one if not two of those in the "competitive disadvantage" thread. These people come on the forum regularly and say something to the effect of "I almost gave up trying". If JRiver isn't interested in making a small effort to accomodate these people that's fine, but they are your potential customers. ![]() IMHO.Įxample of what Wiki page would look like.Ī large portion of potential customers have no interest in going online for help. For example you open the Wiki and there are groupings of topics alphabetically, but under "B" there is nothing on "Bitstreaming", under "D" there is nothing on "DSP" etc. The rest of the Wiki can stay as is if you want - but the current page setup is not very helpful for someone just starting out with MC. User could contribute to the "explanation of the feature/setting and put in links back to threads on the forum or where ever. Then when you are curious about what some setting does you just go to the Wiki start page and click (on the matching icon in the wiki) say you click "General" and that opens to a new gage with an exact match of the settings you see in the MC program at "Tools>Options>General" and then you click on some setting there (say "features") and that opens a new page that shows the same view as the program but/where you can then click on a feature or setting and a new page opens explaining exactly what that that setting is for (it can have internal links to other pages. I would like to see the Wiki reconfigured so that the main Wiki view page (the one when you click "Support>Wiki") is setup in a tree-like configuration matching the exact look of the tools>options settings page in the MC program.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |