# A few interfaces (datasets) in the same Web UI **URL:** \ **Category:** Uncategorized\ **Tags:** usage, solved\ **Created:** [July 5, 2019, 8:47am UTC](https://support.prodi.gy/t/a-few-interfaces-datasets-in-the-same-web-ui/1745 "2019-07-05T08:47:18Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [July 7, 2019, 6:58pm UTC](https://support.prodi.gy/t/a-few-interfaces-datasets-in-the-same-web-ui/1745/3 "2019-07-07T18:58:40Z")
Yes, that's correct. The dropdown is something we added for the demo to show the different interfaces, but it's not really something that makes sense if you're actually running Prodigy to annotate. Here are two threads where I explain a few more details on why Prodigy is designed to use separate processes for different tasks and why switching between different streams and interfaces in the browser like that only really works for a demo: > [@Change annotation recipe when prodigy is already running](https://support.prodi.gy/t/change-annotation-recipe-when-prodigy-is-already-running/987/2): > > Hi and thanks! smiley Most Prodigy recipes are inherently stateful and they make sure to include an isolated, standalone server, REST API and web application. Switching between interfaces would introduce all sorts of problems and open questions: You’d need to make sure that the answers are stored with the correct task, make sure to re-fetch unanswered questions that were sent out etc. All the logic that orchestrates an annotation workflow happens in Python, i.e. at the recipe level. In most… > [@Multiple recipes same port](https://support.prodi.gy/t/multiple-recipes-same-port/933/2): > > Prodigy will start each task in a separate process that provides the model in the loop (if required), web application and REST API. Each task has its own app, to allow running more than one task independently – that’s why they need to be served on separate ports. There’s not really an easy way to serve several independent web applications on the same port. There’s also not really a good case for why you’d want to switch between interfaces, as this would introduce all sorts of problems and open … That said, if you're mostly interested in having a quick way to start a different task from the browser without having to go back to the command line, you could write a mini app that lets the user select a pre-defined configuration, spins up the Prodigy server in the background and returns the URL to the annotation app (or redirects the user). You might also be interested in Prodigy Scale, our new upcoming project, which includes multi-user functionality, plus a whole bunch of other features. See here for details: > [@sparkles Prodigy Annotation Manager Update // Prodigy Scale // Prodigy Teams](https://support.prodi.gy/t/prodigy-annotation-manager-update-prodigy-scale/805): > > Many of you have been asking about how to scale your Prodigy projects – including how to manage more annotators, how to keep multiple feeds running, and how to make sure your annotators stay in agreement. These are challenging problems that are outside of the scope of the [Prodigy](https://prodi.gy) software itself, so we've always planned an extension product that helps you use Prodigy in larger products. We've been quietly working away on this for some time, so we're excited to finally announce our progress! The … --- _[View the full topic](https://support.prodi.gy/t/a-few-interfaces-datasets-in-the-same-web-ui/1745)._