Wednesday, November 7, 2012

Google search with new features. (Enhanced Sounds)

Summary:
 The main summary of this article is that Google is trying to compete with Siri which is an strong match up. They are both different in a lot of ways for example Siri cannot be too specific about some things that they are talking about or the user is asking. For the example gave in the article is say that in Google search can ask questions like how does the Yankee stadium look like? Does things are some question that Siri cannot answer properly. But the other difference is that Siri can do things that Google search cannot which is making appointment, reminders, etc. So there is a difference between using Siri and Google search. For the IOS things it cannot participate with another third part application, which in this case is Google search. So there are advantages and disadvantages between the two features. So it only comes down to whether you should use Siri or Google search I think it's all up to the user and see if he/she is use to which application.

Major Concept
  • Showing how technology is changing overtime.
  • Showing the difference between Google search and Siri and let the user decide which one to use.
  • Showing how people are trying to catch up to each others technology.
Potential Strengths/Advantages
  • Help people with disability to use smartphones.
  • To put that feature on other smartphone too not just iPhone.
Potential Strengths/Disadvantages
  • People will be very lazy in the future.
  • They need to make it more accurate so people who have accent can't really talk to it.
Discussion Question
  • How are all voice recognition made?
  • What other questions that are hard to answer, could it be asked and answered?

http://www.macobserver.com/imgs/teaser_images/20120627android_siri.jpg
Citation:
Cheng, Jacqui. "Google's "enhanced" Voice Search Lands in IOS App Store." ArsTechnica. N.p., 31 Oct. 2012. Web. 7 Nov. 2012. <http://arstechnica.com/apple/2012/10/googles-enhanced-voice-search-lands-in-ios-app-store/>.

No comments:

Post a Comment