You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Alex noted, and I agree with, the ROBOKOP question-builder page is kind of a disappointment after visiting the spiffy main landing page. I'd suggest that this be redesigned as follows:
Increase the font size and general width of the header, including all buttons, using a color scheme for the text and background that matches that on the main landing page.
Consider repositioning the buttons, perhaps as a column on the left, similar to the main landing page.
Replace the text "ROBOKOP" with the ROBOKOP logo from the main landing page.
I don't know what this is called, but for the tab display, use the same one that is used on the main landing page (see below).
Increase the font size for the funding statement.
While these are largely aesthetic changes, I think they're important, as they impact user (and funder) impression. Moreover, if the question-builder page looks professional, then users will be willing to spend some time playing around with queries; if the page looks amateur, then users are likely to quit the very first time they become frustrated.
That said, I don't know how difficult it is to make the changes I'm suggesting.
The text was updated successfully, but these errors were encountered:
I think this may be easier to discuss via Zoom, just so I can show you what I mean. Also, I don't see the fixes for 4 and 5. But let's try to schedule a short (15-minute) call.
As Alex noted, and I agree with, the ROBOKOP question-builder page is kind of a disappointment after visiting the spiffy main landing page. I'd suggest that this be redesigned as follows:
While these are largely aesthetic changes, I think they're important, as they impact user (and funder) impression. Moreover, if the question-builder page looks professional, then users will be willing to spend some time playing around with queries; if the page looks amateur, then users are likely to quit the very first time they become frustrated.
That said, I don't know how difficult it is to make the changes I'm suggesting.
The text was updated successfully, but these errors were encountered: