Most of us tried to use one or more bioinformatics prediction services. We probably all have came across good and bad ones. How do you decide which one to use? What features make it more/less probable that you would stick to one? Let's assume that the underlying algorithms have the same performance.
Some viewpoints that could be discussed:
- description of the algorithm and server
- input and output format, downloading
- error handling
- batch prediction
- reliability of server availability
- date of last update
... any other criteria that you could think of?
And if we do not assume that the performances of the algorithms are the same: have you ever chosen a service that you knew have lower accuracy than an other? Why?
EDIT - I see, I wasn't clear enough, this is one of my answer for a comment.
My question is not about the performance of the predictions but rather how to make their usage user-friendly by setting up webpages that are easily usable, stable and provide all the features that would help the work of a user (both other bioinformaticians and experimentalist researchers).
As for me, I do now want to create such a service/serve/web page just for myself to play with and create a paper, but something that are really useful for others. I think many of us stumbled across pages with poor documentation, impossible input/output format or visualization, etc. I have also heard and read complaints from experimentalist of services that may be straightforward for bioinformaticians, but hard to use for them. I would like to assess the needs of potential users and experts who have already have experience using these things and collect good and bad practices besides what I had seen.
I have just found the expression , it's user experience design.