Scheduling Google Search

Scheduling Google Search and getting the results on your Mobile.

I was reading an article on Tech Crunch about Google and I got an idea. If it is Google it has to be Search. If I see the web site I see it perfect. There is nothing a person would want ; a simple User Interface with text box and button. But what if I don’t have access to internet tomorrow just in case if I am traveling or not at my laptop or not having access to internet in but I know that I will need it to search something. For example when I am in Mysore Road (Let's say Wonder La) and I might be looking for some information on the good restaurants around. And I saw myself imagining the Google page with a “Schedule” button which allows me scheduling the search in future (may be 2-3 days in future) and not only this but also delivering the top 10 or 15 search result onto my cell phone. This sounds cool I suppose.

Now this feature will really be good and handy but I also think how many users will be like me needing Google Search at a real weird time? :)

Comments

  1. AnonymousAugust 21, 2010

    Great idea.

    You need it for sure if you stay in States, where world runs on Internet and @ its speed. We faced such problems in day to day life..

    Hope one day we will get such a search engine.

    Regards,
    DK

    ReplyDelete
  2. Nishant VermaAugust 21, 2010

    Hope one day we will get such option in Google :)

    Thanks
    Nishant

    ReplyDelete

Post a Comment

Your comments will be reviewed and then published !

Popular posts from this blog

Defect Tracking System – Wastage of Money & Time ???

Image
As a QA I have been logging bugs since 5 years. But what do we do with that ? A typical flow: If this is the only thing we need to do then why taking so much of pain to have a defect tracking system . To log a standard bug (Standard Bug= Broken Functionality), we need to write steps to reproduce, pre-requisites (if any), expected result, actual result, priority, severity, snapshot (if any), Test environment details and finally save it. This takes around roughly 3-5 minutes to log a bug. To say truth, I have never seen any report coming out of defect tracking system which is of use in analyzing the pattern of bug or finding out any trend in them. All I have seen apart from tracking usage, is the summary of bugs with count based on Priority and Severity. Is that the only purpose of Defect Tracking System? If that is the case then why not use a Google spreadsheet rather then investing money of the company and time of QA in a bug logging system. I am sure if we mine the data which i
Read More »

The 3 qualities that will always help you become better at almost anything…

Image
Have we ever noticed how excited we are when we start anything? But it’s a sad fact that 70% of people abandon what they have started with so much energy and love. It could be as small as building a hobby or starting a pet project or even an activity or a side learning we started. “ Well begun is half done .” Aristotle did say this but we are judged for how we have finished something. You separate yourself fro m  the masses when you choose to give that task a finish.  The first quality is finishing off what you started and it helps develop mental stamina or willpower.   It builds confidence and inculcates as a habit in a long run. You don’t need to sign up for the mammoth activity to build this habit, even finishing mundane day-to-day routine tasks will help. Diligence — the quality of working carefully and with a lot of effort Diligence is a quality that almost never will get unnoticed. It’s one of the underlying traits of great works or success. The key to mediocrity on the o
Read More »

Test Case Paths : Happy, Sad & Bad

Image
I came back from the background of writing test cases which were categorized in either Positive or Negative test cases. Positive test cases were business flows which may or may not give any result but they will certainly not give any exception or error. Negative test cases are those test cases which were bound to result into some exception or better expressed as error causing scenarios.  Then those positive test cases were prioritized as High/Medium/Low . Finally it used to result in quite a comprehensive test case document. Then it will go through the process of review and few more updates or change of priority etc. Certainly it is a tedious process. Here in ThoughtWorks I got introduced to different way of categorizing test cases called “ Happy/Sad/Bad ”. A test case which results you in a positive result is a Happy path , for e.g. entering proper username and password on login page. A test case which yields no result like entering invalid username and invalid password on a logi
Read More »