At least I know quite some biologists that can do outstanding data interpretation as soon as the data is in Excel, but they don't know how to handle a gzipped fastq files. I don't think about bioinformaticians when thinking about GUIs, but someone not able or willing to use CLIs.
Also, if the software is open source, would you be willing to pay an individual developer a one-time cost for binaries and email support? Thanks for your time.
Examples of interfaces (Python and Qt) I've developed in the past (while working in academia).
1 answer
Also, if the software is open source, would you be willing to pay an individual developer a one-time cost for binaries and email support?
Personally, no, assuming said software is also documented and/or commonly used. I'd rather pay for the time for someone internally to learn how to use it properly, given that no tool is so overwhelmingly critical that paid support is necessary. And if it's open source, why would I pay for binaries? If it's that big a pain to install properly, I'm likely to look for other options first.
As for GUIs, they're almost never necessary in my mind, though they can be very helpful in some cases (cloning software, previewing plots, etc).
Log in to answer this question.
There's definitely a market for GUIs. Note, that you'd enter a field where you compete with organizations with notable sized development teams, for example Galaxy and some dedicated bioinformatics companies.
Thank you. I'm thinking smaller scale and not looking to compete with larger teams or companies, i.e., focusing on a single program to begin with.