In addition to Drag and Drop mechanism for job building (which is amazing and makes it so clear what is going where and disinclines the user from queueing jobs which don’t have correct inputs etc), it would also very often be more useful/practical/swift to be able to modify the inputs by text alone, such that you could simply clone then change the class_6 to class_7 and immediately fire the job off. I’m sure it’s technically impractical to implement, but I constantly find myself in situations where just changing a value in text ala Relion would be much faster, and drag/drop seems cumbersome. Perhaps ideation for Cryosparc v5 or v6. was envisioning an “advanced” toggle in job builder that makes all to modifiable text, so could drag drop the first instance then lightning fast text edit the inputs to redirect them to other values.
Would be great if some jobs didn’t allow submission without critical parameters set, though. Nothing worse than queuing a load of jobs to have an early one fail because, e.g. filter resolution was not set! 
…
It’s a little amusing, though, that as more features and flexibility are added (even for advanced users) CryoSPARC is drifting away from “easy to use”, which was one of the original big ticket selling points for users. This is a natural result of increased functionality. It’s less of an issue if you can “right click through” the whole process (local refinement is usually missing as an option, which I’ve been bumping into a lot recently). Again, I’d reiterate my request for a custom option in the right click menu on that one…
But some of the issue is not. From the somewhat scattered/messy list of job types (e.g.: most users do not need benchmarking and validation job types, and if using 16-bit MRC CTFFIND no longer works, etc…), to functions within jobs which cannot be changed but are still exposed to users (e.g. mask type, noise mode or CPU/GPU mode for filtering) some of the UI could do with a tidy up.
The card view is brilliant, and live visual feedback on progress was a game changer, but one of the comments increasingly received from younger (Masters/Ph.D student with the occasional final year undergrad) training course attendees now is that the list of job types is overwhelming and the options within them confusing as “advanced” mode often needs to be used to expose useful options.
Now, at least some of that is language barrier, being in Japan. I don’t know how realistic adding translations might be (if everything is hard coded in English, it’s a nightmare) with, e.g. a dropdown menu in a corner to change on-the-fly…
Honestly I would just get rid of advanced mode - particularly in its current form as an unlabeled checkbox. It is confusing, not discoverable, and a lot of the “advanced” features are used in standard workflows these days, so I would be inclined to either just display everything, or only hide really niche features.
Yup, along with either removing unchangeable options or making them editable.