EDIT: disregard. This didn't work when I tried before typing this out, but after a refresh i can get multiple installations and sets of devices working no problem.
Lots of apps allow multiple instances to exist together listed on the Apps page in something of a parent child arrangement, like multiple dashboards for example. I seem to always have a few weird projects in progress at a time that often rely on maker API to poll a list of attributes for devices or to send commands to certain kinds of devices, a Wear OS app with a slider that sets dimmers for example. Every time I am trying a new project on a new platform and need a specific subset of devices I have to spend a bunch of time figuring out how to work with json on a watch or a calculator or mobile app or whatever it may be just to avoid listing motion sensors in a list of dimmers because my MakerAPI "everything" URL has to include every device that's used in ANY of my integrations, rather than being able to make a child Maker API authorization that only includes devices I need / where the HTTP request wouldn't return a bunch of devices I won't be using anyway. Not that json file sizes are extreme or anything, but as a matter of efficiency, it does bother me that every time I hit that URL to update the current value of attribute A for devices with capability Z, I get a json response with 20x more devices than the project needs and have to parse all that useless info, sometimes on devices with limited resources or storage, or limited wifi bandwidth or speed.
Dashboards and MakerAPI aren't that different when you think about it, the former is basically the GUI version of the latter. I can make a new dashboard and only authorize certain types of devices for it, but for MakerAPI I cannot.
