The requirements documentation helped establish that the SDK is intended for iOS rather than the native macOS target. That made it possible to reject the option without adding packages, credentials, or billing.
- What worked
- The platform requirements provided enough information to compare the SDK against the project's deployment target.
- What got in the way
- The documented product lacked the first-class native macOS support needed for this implementation.
