to broadcast the transaction to 3 peers you need to connect to a different protocol
You don't connect to a protocol, you connect to a server. If someone wants to use your service he'll have to connect to your server, so I can't see any difference.
Connecting to Bitcoin peers requires using the Bitcoin Protocol, which requires making a different type of connection. Using a dedicated HTTP server on the other hand requires only doing a regular ajax request to a remote server with the details of the transaction.
This tiny difference is what makes it easy for new developers to come in and create new tools - the simpler tools that you can provide to developers the more developers you'll have working on this. Remember, time = money, so business makers who ask devs "how long will X take you to do with Bitcoin?" and the dev answers "a lot" because it requires doing different complicated
things, and if it's cheap you'll have more people putting money into Bitcoin related projects.