ACS built their own copy of our submission system. We have received requests from potential members to do the same, so the submission system fits into their existing processes and branding.
Problems with externally developed tools:
Large amount of work to ensure the initial API interactions are correct
Maintenance burden for a complex API interaction
External users cannot keep up with our feature development, so their tools will always lag
Possible solutions:
Separate our submission system into a distinct application. External users could install this application in their systems, and customize it if needed. We could publish updated versions regularly. Of course, this adds some maintenance burden for us in our regular processes.
Allow greater customization of the submission system, per journal and per institution. Colors, fonts, etc.
ACS built their own copy of our submission system. We have received requests from potential members to do the same, so the submission system fits into their existing processes and branding.
Problems with externally developed tools:
Possible solutions: