Thanks, all, including aniqim!
I suspect the problem is that most people here are operating with the independent developer mindset.
(I shouldn't complain, since effectively I've been doing that too, for decades ... the advantage of having a small
However, I've seen a lot of corporate projects / multi-developer projects, and haven't seen one where we'd buy a plugin (DLL, library, etc) that's intended to go *into* the product (app/program/etc.) and where we had to pay per developer.
(Buying an IDE, or compiler, or editor per developer, yeah, but somehow that's different.)
Ah ... got it: I see charging per developer as normal/acceptable for *tools*, but not for things that go *into* a single product.
(Obviously, group/site licenses are alternatives to per-developer charges ... I've bought those, too.)
For per-product items, I have no philosophical problem with a mechanism (e.g., code or licensing) that prevents using the per-product purchases in more than one product (which would be piracy)!
I've also seen charging developers a per-end-user charge, that's really bad.
(IIRC, some third party Amiga C compiler tried to do that in the late 1980s ... they weren't successful,
and I've seen one or two mainframe compiler vendors try to do that.)
I'd posted in the hope of discovering that Corona Labs marketplace did, indeed, have a mechanism of registering a given plugin as "per-product", thereby allowing multiple developers to build with it.
BTW, the reason we want two developers to be able to build is that I absolutely abhor the Apple cr*p involved with certificates, profiles, etc., and every time I need to get a new profile/whatever, I lose 2 to 3 days. So, I now have a second developer helping me, and one of his tasks would have been to do the Apple builds while I do the Android builds. (I'd originally thought of having him do both, but I realized belatedly that the plugin was registered to my personal account, and I (a) wouldn't let him use it, and ( can't (per Corona licensing limits).) I suspect we'll just bite the bullet and buy a second set of all the plugins, to make life easier.
Also, if you think about it, there's another reason the failure ...yes ... to provide some mechanism to allow this is bad: it theoretically screws a development team where the build computer dies. According to the Corona SDK license, one has to deauthorize the build computer *from that computer* before moving the build account to another computer.
(Yeah, I don't think Corona actually checks this ... but that's not a valid counter argument in this discussion.)
In short, plugin authorization should be re-thought, as well as Corona SDK licensing.
P.s.: when I say I've been programming for 50 years...that first year was FORTRAN IV, so does that count?
P.p.s: Hey, I'm still struggling with accepting the concept that the same program might cost more on a 100 user mainframe than on a 2 user mainframe ... especially if its operation isn't related to the number of users (we used to see this a lot in the HP 3000 MPE marketplace)
P.p.p.s: darn forum software complained that I had four instances of colon parenthesis (I can't put it here, as that would get counted), and said I had "too many emoticons". Sheesh. At least I've cut back on my exclamation points!