The Future of Siri

My quick thoughts on where Siri could/might go, and some questions that are yet to be answered by Apple.

[list type=”circle”]
[item]Why, when Siri is activated, does she beep twice rather than greeting you with speech? (ie hello name)[/item]
[item]If Siri gets its own API, will it be strangely reminiscent of AppleScript?[/item]
[item]At what point will some apps become more useful via Siri than having their own dedicated UI?[/item]
[item]Will developers be charged an access fee if they call on Siri for advanced actions?[/item]
[item]Will Siri be able to communicate with Siri on another device? For example can a user ask an iPhone based Siri to delegate to multiple decision based devices?[/item]
[item]Will system wide integration be the first step toward the duplication of key app functions that might force them to fade away, for example tweeting?[/item]
[item]Will Siri learn to interpret data so that she can recommend products to you? Birthdays and anniversaries come to mind.[/item]
[item]If Siri is fluent in other languages, will she eventually teach them to the user?[/item]
[/list]

6 Comments

Join the discussion and tell us your opinion.

no
June 27, 2012 at 08:06 AM

1. Network Traffic.
2. C API. Look for SiriProxy. AppleScript is a language, not API.
3. Key Phrases can be passed down to the app if you register them. that is all. see SiriProxy.
4. No
5. No. IOS 6 already has tweeting usng Siri.
6. Simple things like happy birthday but picking a gift for you, probably not.
7. No.

Siri is a fake AI. It is using conversation
to make it easy for you to talk to it.
It is just grammar interpreter with statistical guessing to give you answers. try not confuse it with other things.

Matt Binkowski
June 27, 2012 at 09:06 AM

Hi.
Thanks for the responses. Some of the things I wrote were more “what ifs” rather than what will be in the next rev of iOS. As for the AppleScript line, I know it’s not an API, but it could be an interesting way to influence how the API could evolve.

no
June 27, 2012 at 01:06 PM

If you look at SiriProxy. The developers register a phrase. when Siri hears the phrase.
it sends a message to your proxy. proxy does the work. and sends the answer
as a sentence which Siri then speaks.

It is upto Apple to design or limit this per developer or task.
most of SiriProxy examples are home automation, car starting, etc.
It Apple wants to go into Apple TV then they will most likely won’t let you do even that
because next step would be home automation.
then again Siri lives in the cloud and running your tv when internet is down is major flaw.
So it best to keep Siri as another input method like hands free.

Matt Binkowski
June 27, 2012 at 02:06 PM

I need to register as an apple Dev. Im not one today but would love to learn how.

no
June 27, 2012 at 06:06 PM

Best thing I can say regarding development is to
try learn to problem solve. write down step for something
is detail a fashion as possible (like going from point a to b).
Learn a language like C, Python, Ruby.
Try taking comp sci or electrical engineering if you are going to college.
Learn how processor works, compiler, data structures, math algorithms, etc.

If you don’t have introvert brain then it is best you pursue some
other career. Sure you can be hacker and learn by example
but won’t be happy doing it.

good luck.

Matt Binkowski
June 27, 2012 at 08:06 PM
– In reply to: no

Can I ask who you work for? I’ve got a learn c on the mac book and thought I’d start there. I definitely have the interest and experience architecting digital apps (see my portfolio in this site).