But Apple already justified building a secure, private, on-device SDK that exactly one (1) company will be guaranteed to use.

I see no reason it cannot be a private entitlement similar to the other sensitive entitlements on iOS.

▲

shuckles 5 days ago | parent [-]

Internal API is not an SDK. It regularly astounds me how many commenters on a so-called hacker forum seem to think it is. Is everyone else publishing their tightly coupled business logic code as API these days? Is that what GraphQL is?

	▲	zrobotics 5 days ago \| parent \| next [-]
		I would hope that security critical parts of the OS that can't be exposed as an API aren't being used to communicate with the apple watch. Why would the apple watch need access to these APIs that can't be publicly exposed? Is there any reason beyond apple wanting to make sure other smartwatches are second class citizens in their ecosystem? This isn't exposing business logic, this is an operating system vendor deciding what it exposes to vendors. There is clearly an API that the apple watch is using to communicate with the OS, why shouldn't other vendors be allowed to access this?
	▲	bigyabai 5 days ago \| parent \| prev [-]
		Apple can revoke the entitlement if it's abused, as they've done many times in the past with signed apps. Nobody (including the EU) is demanding that it be an zero-auth free-for-all API, only that competitors can use it. It's not an absurd demand and there is absolutely precedent for Apple individually trusting competitors in this regard. If you're astounded by hackers asking practical questions, maybe you should stop carrying water for corps and see how your back feels. Let's talk shop, what are the roadblocks Apple faces here?