The developer of the software supporting those platforms. In this case, Beeper.
I suppose if Apple wants to say certain users are not allowed to access iMessage unless they've bought an iPhone that's fair. (Maybe you could argue its anticompetitive to bundle services together like that, but I won't assert that point here.) But if that's all this was about then I ought to be able to buy an iPhone, import the access token from that into Beeper on my Android, stuff the iPhone in a drawer, and go about my business. The problem is that Apple wants to dictate not only who has access to iMessage servers, but also how they're allowed to access it. And that is unacceptable in my opinion.
"Security" is a poor excuse. If server side software has to rely on trusting the client then it was never secure in the first place. And if client side software wants to "secure" itself against the person who owns it... that's a form of "security" I could do without.
The developer of the software supporting those platforms. In this case, Beeper.
I suppose if Apple wants to say certain users are not allowed to access iMessage unless they've bought an iPhone that's fair. (Maybe you could argue its anticompetitive to bundle services together like that, but I won't assert that point here.) But if that's all this was about then I ought to be able to buy an iPhone, import the access token from that into Beeper on my Android, stuff the iPhone in a drawer, and go about my business. The problem is that Apple wants to dictate not only who has access to iMessage servers, but also how they're allowed to access it. And that is unacceptable in my opinion.
"Security" is a poor excuse. If server side software has to rely on trusting the client then it was never secure in the first place. And if client side software wants to "secure" itself against the person who owns it... that's a form of "security" I could do without.