vrtcl1dvoshun

@Vitor Thanks for the informative reply! To further clarify my thoughts, while I certainly don't expect for every single workflow out there to be contributed to a central repository (I imagine there'd be an issue in dealing with pseudo-redundancy), I do maintain that there should be an official (as in blessed by the developers of Alfred) means to do those things I've already mentioned. As it currently stands there isn't. I imagine it to be in their interest to at least make it an option. A point you already made best states the reason: "I want to build and share more workflows, not spend all my time making sure they’re all up-to-date on every third-party reference site" I understand that people don't always want to adhere to an opinionated way of doing things, but a little opinion goes a long way in increasing the productivity of everything that we do. After all, we do both use an opinionated operating system with good reason.

While you've provided good advice, I'm not a developer. I just want to use the workflows that have been made available and not have to scour the internets for updates. Not every workflow has been setup with this process. As I see it, there needs to be a standard for: where you keep user settings for updating the workflow for finding new workflows documenting what the workflow does documenting what needs to be changed in the workflow (i.e., user home folder, username, etc.) what version the workflow is currently at (visible in the Alfred preferences pane) I'm sure others could add to the list. My biggest frustration is that I feel like the developers of Alfred didn't forsee the collaborative community that would develop around workflows. As it currently stands, there is a forum (a forum!) that is being used to post workflows and their issues, feature suggestions, updates, etc. What an incredibly ineffective and inefficient means of communication for the development, support and distribution of workflows! You mentioned Alleyoop. From what I've gathered from the forum and its original developer, phyllisstein, it is deprecated. When I tried Monkey Patch, the vast majority of workflow had the error "Could not check for updates." Hear me when I say that I'm not criticizing either developer—they've performed the work on their own time and no other person that comes up with a workflow is required to use their system. A workable solution here should come from the developer and the developer only—this will ensure that others can be confident in their using it. Since there is no point in continually remaking the wheel, there needs to be an accessible and user friendly central repository from which any user can browse, download and update any workflow or theme. The repo should allow user feedback and submission of bug reports. It should be searchable and up-dateable from Alfred's interface. It should allow contribution from those who want to contribute. GitHub could be a fine answer to all these suggestions; perhaps there is something else, but IMHO any solution is better that what we currently have.

Need the ability to add a version field to keep track of workflow changes and prevent updates from wiping out user customizations. If not, then I suggest developers at least add their app's version to its name as follows: "My Alfred Workflow (2.3)" which would remain consistent with the way Apple denotes different app versions. The version number should show up in both the filename of the workflow and in the name that is seen in Alfred's workflow preference pane.