Open Radar

 
Summary:
SiriKit usage is limited to a small number of types of applications, rather than being available to all applications.

Steps to Reproduce:
1. Have a parking app you are really excited to add support for Siri for, since many of your users would benefit from the safety benefits of booking parking with voice rather than by touch while driving. 
2. Read documentation. 
3. Have sad. 

Expected Results:
Complete steps 1 and 2 as previous.
3. Start building awesomeness with SiriKit
4. Happy users!

Actual Results:
This is the current text of what’s supported in SiriKit, per https://developer.apple.com/library/prerelease/content/documentation/Intents/Conceptual/SiriIntegrationGuide/index.html#//apple_ref/doc/uid/TP40016875-CH11-SW1: 

Add SiriKit support only if your app implements one of the following types of services:

Audio or video calling
Messaging
Payments
Searching photos
Workouts
Ride booking

Notes:
I’m the lead dev for http://spothero.com, which facilitates finding and paying for parking spaces. We (and our competition in the parking business) are a crystal-clear case of a place where Siri support would be beneficial to both the convenience and safety of the users, but with the current guidelines we would need to somehow contort ourselves into the “ride booking” or “payments” category to be able to leverage the API. 

While my overall argument is that this restriction should be dropped entirely (My partner and I would really love to be able to add a “Siri, record me a Hum” to my side project, http://justhum.com, for example), parking is a case where usability would be so significantly enhanced, I’m not really sure I understand why it’s not in the list of application types not permitted to use SiriKit.