The task interface is a working tool for your performers. The more convenient and helpful it is, the less opportunities there are for the performer to make a mistake. In general, crowdsourcing task interfaces should adhere to the principles of good UX design. When planning out your interface, always think about how performers will be approaching the task:
  • They have access to many tasks at a time and can choose between them.
  • Their earnings depend on the amount of tasks done, so they are motivated to perform fast.
  • Most tasks are monotonous and involve repeating the same actions.
  • Loss of concentration provokes mistakes.

Here are a few principles of performer-friendly task design:

Provide a cross-platform interface

Users access crowdsourcing platforms from computers, tablets, and smartphones. If a task is displayed correctly on all devices, more people will see it and complete it. To adapt the task interface to different platforms, make sure there are no useless empty spaces, texts fit on the screen, and so on.
However, not all tasks work well as cross-platform solutions. Tasks that involve complex manipulations on the screen, loading videos or displaying media content might not work well on different devices or will demand too much traffic. It’s better not to include mobile access for these types of tasks.
Provide keyboard shortcuts
Shortcuts can be assigned for any action – setting a verdict, playing or pausing a video, or opening a link. The simplest tasks can be completed exclusively on the keyboard, which helps performers complete them much faster. If the interface supports shortcuts, describe them in your instructions or display them in the task interface.
But don’t forget to delete shortcuts for mobile interfaces: they are useless there and will just take up space, which is already limited on a mobile.
Check required actions
Performers usually work fast and might skip important steps, either accidentally or intentionally. Since a task interface is basically a web page, required actions can be checked by using Javascript methods. If a task involves watching a video, visiting a link or typing in a text, it’s a good idea to block the user from submitting the task until the required action is done. Recording performers' actions is also a basis for quality control (to learn more, see the Quality Control page).
Eliminate interaction with external resources
Navigating through external resources takes additional time for loading the page and can distract the performer from tasks. It is also inconvenient for you, as the requester, because you can’t track what the performer is doing on the external page. It’s better to use a screenshot or a copy of the data saved in stable storage (like cloud storage), or at least integrate external pages via an iframe.
Strive for minimalistic design
It’s always better to strive for minimalistic design to prevent fatigue. Performers might get tired of excessive colors and textures while working on a long flow of tasks and lose their focus.
Use space reasonably
It is always better to put all elements within the area of one standard monitor screen. This allows a performer to evaluate tasks without scrolling. Any elements that are logically related (like checkboxes) should be grouped together. The most important information should stand out visually. Less important information can be hidden or displayed as a popup tooltip.
Remove excessive elements
All the interface elements should be actually necessary for the task. It can be tempting to add extra reference links to different services, but it’s better to decide which ones are really helpful and remove or reduce the size of others.
Arrange a convenient task page
One page can contain several separate tasks, which is convenient if the tasks are simple. It’s even more user-friendly if separate tasks are of the same width and there aren’t any wide gaps between them. There shouldn’t be more than 3 tasks in one row — one task per row is ideal.
Test the project
This seems to be a simple yet golden rule for any web launch – before opening a project for performers, make sure that everything works as planned.

Toloka platform offers different ways of putting up an interface

  • Template Builder: a tool that allows to create interfaces from off-the-shelf components adapted both for desktop and mobile.
  • Interface Editor: separate HTML, CSS and JS blocks that can be configured separately. Be sure to use special components and helpers for the HTML block as well as the JavaScript extensions, both described in the Configuration Guide.
Toloka News
Receive information about platform updates, training materials, education events and other news.
Wed Apr 28 2021 16:35:10 GMT+0300 (Moscow Standard Time)