Mad4 Mobile Phones Orange

From the category archives:

Google

Interesting Google mobile search stats

by Patrick Altoft on April 16, 2007

A couple of interesting pieces of information have been reported after a mobile conference in the UK. The ForumOxford conference in was held in Oxford last Friday and included a talk from Adrian Blair, a Google engineer.

According to Adrian 20 percent of search terms on the mobile (and normal) internet are unique terms that have never been searched for before.

Another useful nugget is that half of the page views served by Vodafone came from the least popular 84 percent of sites.

Via Mobhappy

{ 0 comments }

Google explains how to build killer mobile applications

by Patrick Altoft on April 12, 2007

Google has been outlining its plans for a killer mobile application during a presentation at its plush New York Offices.

The plans, which will no doubt add fuel to the Google Phone rumours, detail what Google thinks a mobile application should do in order to be a success.

The event, called “Google Presents User Experience & Mobile Apps”, was led by Google user experience designer Leland Rechis who wants information to be “universally accessible”.

When Google launch a mobile application they will look at it through 6 layers:

  • 1. Understanding users, anywhere, anytime
  • 2. Fits in your pocket
  • 3. More personal than the PC
  • 4. Consistency across modes
  • 5. Localization is intensified
  • 6. Integrated devices, modes, products

Information Week writer Stephen Wellman was fortunate enough to be at the event and has a great summary of the different user types Google is catering for:

Rechis said that Google breaks down mobile users into three behavior groups:

  • A. “Repetitive now”
  • B. “Bored now”
  • C. “Urgent now”

The “repetitive now” user is someone checking for the same piece of information over and over again, like checking the same stock quotes or weather. Google uses cookies to help cater to mobile users who check and recheck the same data points.



The “bored now” are users who have time on their hands. People on trains or waiting in airports or sitting in cafes. Mobile users in this behavior group look a lot more like casual Web surfers, but mobile phones don’t offer the robust user input of a desktop, so the applications have to be tailored.



The “urgent now” is a request to find something specific fast, like the location of a bakery or directions to the airport. Since a lot of these questions are location-aware, Google tries to build location into the mobile versions of these queries.

{ 0 comments }

UK mobile web users prefer Google, Orange and BBC

by Patrick Altoft on March 26, 2007

New research into the browsing habits of UK and US mobile web surfers has revealed that UK users prefer the likes of Google to Yahoo and Microsoft sites.

The research conducted by M:Metrics by analysing the habits of smartphone users mirrors the statistics we see every day on the internet with UK surfers shunning MSN and Yahoo in preference to the BBC and Google. Both Orange and O2 will be pleased to see that their portals were popular with those tested.

In the UK Google has an 80% share of the search engine market with Yahoo and MSN trailing a distant second and third respectively.

From the press release:

In both geographies, Google ranks as the most popular mobile Web site, the 8 a.m. to 5 p.m. daypart has the largest audience of mobile Web users, and mobile media consumers spend more than eight minutes per session accessing the mobile Web, a surprisingly high figure. However, while mobile operator sites are most popular among British consumers, Americans prefer Yahoo! and Microsoft properties.

{ 0 comments }

Google Cell Phone patent: searching without a browser

by Patrick Altoft on March 22, 2007

Yet another Google Phone patent has emerged today, this time detailing a method for a cell phone to retrieve and display data from the internet without using a mobile browser.

The patent is complex so you may wish to read Bill Slawski’s excellent summary rather than the actual patent document.

Essentially the patent discusses a software application that allows users to search via a mobile phone and receive search results without using a conventional mobile browser. The software will have predictive search technology (see picture below) and automatically reformat web pages for viewing on the screen. Google also mentions why they want to do this – opening up a browser is slow and for search to be accepted as an integral feature of the phone it has to be quick and easy. Think of this application as a search box on your PC desktop rather than the search box in your web browser.

Customized data retrieval applications for mobile devices providing interpretation of markup language data

Handheld mobile devices, such as cellular telephones and personal digital assistants (PDAs), are becoming increasingly powerful both in terms of processing power and the ability to provide access to data. The usefulness of these enhancements is often limited, however, by an inability of mobile devices to display data effectively due to the small size of the display and the limited memory resources relative to laptop and desktop computers.



[0004] Systems and techniques are provided for retrieving and displaying information on a mobile device by integrating markup language rendering functions into a specialized data retrieval client application.



[0005] In one general aspect, information is retrieved to a mobile device using a data retrieval application installed on the mobile device. The data retrieval application includes instructions for presenting a structured data display on the mobile device, defining a structure of the structured data display, requesting selected hyperlinks included in the structured data display, and rendering markup language information received in response to the selected hyperlinks. A user request to retrieve data is received through the data retrieval application. Data is retrieved in response to the received user request. The retrieved data is displayed according to the structure of the structured data display, and a user is able to select a hyperlink in the displayed data to retrieve and render markup language information using the data retrieval application.



[0006] Implementations can include one or more of the following features. The data retrieval application is a search application or an electronic mail client application. A search user interface having a structure defined by the search application installed on the mobile device is displayed. The search user interface includes a predefined field for a user entry of a search query, and the user request to retrieve data includes a submission of a search query. The structured data display defines a structure of a search results user interface for presenting data responsive to the search query. The data responsive to the search query includes a hyperlink. A user selection of the hyperlink is received using the search results user interface, and a request for additional data based on information included in the hyperlink is sent. The additional data is received in a markup language format, and the markup-language-formatted data is rendered by the data retrieval application for display on a user interface of the mobile device.



[0007] A display of data on the mobile device is automatically adjusted by the search application based on one or more characteristics of the mobile device. The structured data display includes one or more user-selectable features defined by the search application installed on the mobile device. The one or more user-selectable features are operable to perform operations defined by the search application. When a user selection of a hyperlink in the displayed data is received, markup language information is retrieved and rendered without accessing a browser application.



[0008] In another general aspect, a data retrieval user interface is displayed on a mobile device. The data retrieval user interface includes a structure defined by predetermined data stored on the mobile device. User-defined information is received through the data retrieval user interface. A data retrieval request including the user-defined information is sent to a predetermined remote location. A response to the data retrieval request is received, and the response includes retrieved data. A retrieved data user interface is displayed on the mobile device. The retrieved data user interface displays the retrieved data in accordance with a structure defined by predetermined data stored on the mobile device, and the retrieved data includes one or more hyperlinks. Markup-language-formatted data associated with a hyperlink selected by a user is retrieved, and the markup-language-formatted data is rendered on the mobile device without accessing a separate browser application.

Customized data retrieval applications for mobile devices providing interpretation of markup language data

{ 0 comments }

Google has filed a patent application describing a method of using multiple sessions to make searching for information via mobile phone much faster than the current system.

The Overloaded Communication Session patent application was filed on 21st July 2006 and published on 1st February 2007. The document discusses how mobile devices can connect to the internet and retrieve documents and search results. The patent is quite complex but in general Google appears to be patenting a method of using more than one connection to return search results. For instance a user could see the first 5 results from one session and the second 5 results from a second session.

If Google decides to create a phone then search will be integrated into a lot of the applications and speedy information retrieval will be essential. Google has always made sure their internet search pages work as fast as possible and will want to do the same on any mobile applications they create.

Abstract:

A method of providing information responsive to a request from a wireless communication device involves receiving an information request from a mobile device and generating responsive information for the information request, transmitting a first portion of the responsive information to the mobile device in a first communication session, and transmitting a second portion of the responsive information to the mobile device in a second, overloaded communication session.

Google Phone session patent

Summary & Implementation:

In one implementation, a selection of a result element may be received in response to display of the first set of results or the second set of results, and transmitting a text message in response to the selection. Also, a selection of a result element may be received in response to display of the first set of results or the second set of results, and a web page request in response to the selection. The receiving of the the first set of results and receiving the second set of results may also be performed by separate execution threads on the mobile communication device.



In other implementations, the first set of results and the second set of results may relate to multiple different search types. The multiple search types may be selected from a group consisting of advertisements, images, web pages, maps, news, geographically specified (local) content, shopping, weather, and content resident on the mobile device. Also, the multiple search types may be displayed as display elements categorized by search type, and each category may be displayed separately. One search type may also be displayed with another search type.


In addition, navigation between the multiple search types may include horizontal navigation. Search requests for the multiple different search types may also be generated in response to entry by a user through one entry point in a user interface. In yet another implementation, a computer program product containing executable instructions that when executed cause a processor to perform certain operations is disclosed. Those operations include overloading a connection between a mobile device and a server, wherein the overloading comprises transmitting a search request from the mobile device to the server, receiving at the mobile device from the server a first set of results associated with the search request, and receiving at the mobile device from the server a second set of results associated with the search request.

Via Search Engine Land

{ 0 comments }

Google hires Sidekick team to build Google Phone

by Patrick Altoft on March 21, 2007

Google has been in talks with several European mobile phone companies, including the manufacturers of the T Mobile Sidekick, with regard to the rumoured Google Phone.

According to an article in todays Guardian Google has hired the creators of the Sidekick to work on the Google Phone.

Google, meanwhile, has held talks with companies including Telefonica, owner of O2, about producing a “GPhone’”which would make it easy for users to search for information using their mobile handset.



It is believed to have hired the team who created the Sidekick mobile device which T-Mobile launched more than two years ago. The device, which has a keyboard hidden beneath a swivelling screen, gained notoriety in the US when a phone owned by Paris Hilton was hacked into and her address book posted on the internet.

{ 0 comments }

Could the Google Phone rank search results by call volume

by Patrick Altoft on March 21, 2007

Our post about the Google phone patent discussed how the rumoured device could predict your search patterns based on your history, location and other known variables. Looking back at this patent and some of the comments made there were a number of features not mentioned that Google may be considering for the Google Phone.

Firstly, Google has indicated that the phone will be designed for the developing world rather than being a high end device. I don’t buy this. I believe that Google will develop a software application (Google Mobile operating system) that can be used on both low and high end devices and customised depending on the type of phone it’s being used on. They already spent a lot of time developing the bespoke iPhone application which is bound to make other manufacturers want some customised Google magic on their handsets as well.

Google makes most of its revenue from selling advertising but this isn’t easy to do on a mobile phone. My belief is that they will show location based adverts, as discussed in the patent, but using a click to call feature where the advertiser pays when the user rings them. Costings will be based on the same model as Google Adwords with local businesses bidding to appear higher up the results. Crucially there will be a section of non paid results, just like the main Google search results has on the Internet. After an initial seeding based on distance from the user Google can rank these search results based on the number of past users who have called each number.

Obviously this method of searching and ranking businesses by call volume isn’t going to be much use for some queries but for a user in London wanting the best pizza restaurant within 500 yards it should work very well.

Thanks (again) to John from wood burning stoves for the tip!

{ 0 comments }

Google Phone finally confirmed, sort of

by Patrick Altoft on March 15, 2007

After much speculation Google seems to be admitting that a Google Phone is on the cards but it doesn’t appear to be the iPhone killer we were expecting.

Apparently the Google Phone is one of many projects Google is working on and might be aimed at developing countries rather than being a high end device.

Engadget reports:

Isabel Aguilera, Google’s chief executive in Spain and Portugal, has admitted that the searchmeisters have some mobile goodness in the works but appeared to play down the project, noting that the phone is just one of 18 R&D initiatives the company currently has underway. Furthermore, she mentioned that Google’s mobile skunkworks were designed to make their way into developing countries, suggesting that this may not be the Samsung sourced, iPhone-killing monster we’d been getting an earful about as of late.

{ 0 comments }

Google phone pictures (probably fake)

by Patrick Altoft on March 13, 2007

In a thread at the Mobile Burn forums MaDnEzZ has posted a screenshot taken while completing a survey online.

I’m signed up to a paid-survey website and well i received this the other day as part of the survey that i was participating in
basically it was a survey about a google phone, which was designed by samsung, but running what seemed to be a google interface, i totally forgot to take a screen shot of the specs but they seemed decent, not mind blowing
had the usual in par of 3g/wifi etc, had a camera 2megapixal from what i recall, feel really stupid for now taking a screenshot of the specs not lol

Google phone

This is what the screenshot says about the Google Phone:

Google makes relevant information and communication tools easily available wherever you are.

The Google Phone brings the power of the internet in your pocket, in a simple and intuitive device. It combines the traditional voice and SMS capabilities of phones with all the exciting Google services from the PC such as Search, Gmail, Maps, Blogger…

The Google Phone, designed by Samsung, is a very thin and stylish handset with a large screen and a QWERTY keypad so that it provides a real internet experience.

All these internet services will be available under a simple Internet monthly flat fee, comparable to PC Broadband products, giving you transparency and control over your mobile bill. Thanks to simple relevant advertising, Google will even give you a 3 month discount on your mobile Internet monthly flat fee.

Mad4mobilephones opinion: its a fake

{ 0 comments }

Our patent gurus have discovered an interesting patent filing from Google that could reveal the applications they are planning for the Google mobile phones. Alternatively this technology could even debut in the iPhone when it is released in June.

Google has become the number one place we go when we want to find something online and the Mountain View based company has been building mobile versions of common applications such as Gmail and Google Maps/Local for some time now.

The patent filing details an application that can predict what a user is searching for or the words they are typing in a text message by taking into account the users location, previous searching / messaging history and even the time of day.

This concept might seem familiar to older Google users. Way back in 2000 an April Fools joke called Google MentalPlex promised to use 1.6 billion variables to predict what you wanted before you searched. Another ongoing project used in Google Labs and the latest Google Toolbar predicts what you are searching for as you type but still doesn’t go anywhere near as far as the Nonstandard locality-based text entry patent filed in 2005.

In the patent Google discusses how all the data is stored on Google’s servers and queries are sent whenever the user is searching for something or typing a message. Presumably the queries would be sent over some kind of mobile AJAX interface.

This patent is truly groundbreaking in what the application could do. Imagine that you are planning a night out in London. At 6pm Google could predict you are looking for a restaurant and, given your history of looking for directions to Chinese restaurants every week, would select an array of suitable places for you to eat.

At 9pm you would turn your phone on again and Google would know you wanted bars near the restaurant. At 11pm Google again predicts you need a list of local taxi firms.

Google Phone Patent

In one aspect, a computer-implemented method of providing text entry assistance data is disclosed. The method includes receiving at a system location information associated with a user, receiving at the system information indicative of predictive textual outcomes, generating dictionary data using the location information, and providing the dictionary data to a remote device. The received information indicative of predictive textual outcomes may relate to search requests made by a plurality of remote searchers. Also, the dictionary data may include a plurality of terms with a corresponding plurality of predictive weightings, and dictionary data may be generated using the information indicative of predictive textual outcomes).

[0009] In one implementation, providing the dictionary data to the remote device may include transmitting the data to a mobile phone. The system may also receive user preferences that are used in searching based on the search results. The generating of the dictionary data may also include producing data related to the information indicative of the user location. The generated dictionary data may be associated with places near the user location. Also, the generated dictionary data may be associated with common query data from users near the user location, and may be provided to the remote device in response to a request from the remote device. The dictionary data may also be compressed before it is provided to the remote device, and the data may include supplemental data for addition to a preexisting dictionary on the remote device.

[0010] In another implementation, the method may further include receiving a search request, generating a search result, and providing the search result along with the dictionary data. The dictionary data may include data from documents relating to the search result. In addition, the dictionary data may include data corresponding to one or more areas in the proximity of the user location, which may in turn comprise location names.

[0011] In another aspect, a data collection and distribution system is provided and includes a request processor to receive data requests from one or more remote clients, a local search engine to search in response to the data requests, a dictionary generator to produce information for use by the one or more clients containing predictive data entry information for the one or more clients, and a response formatter to receive information responsive to the data requests including predictive data entry information, and provide the information responsive to the data requests for use by the one or more clients. The request processor may be operable to receive information indicative of a user location. Also, the local search engine may be operable to extract information indicative of a user location from the data requests.

In one implementation, the dictionary generator may include a concurrence rater that calculates predicted concurrence scores for a plurality of objects, and the plurality of objects may include a plurality of terms that may be entered by a user in generating a data request. The system may also include an object selector to identify objects in a document for submission to the concurrence rater. The local search engine may also be operable to receive a plurality of requests and information indicative of a user location and provide the requests for transmission by the response formatter along with predictive data entry information. The information for use by the one or more clients may include data corresponding to one or more areas in the proximity of the user location, which may in turn comprise location names.

[0013] In yet another aspect, a computer-implemented system for providing information indicative of probable usage of objects by the user of a data entry device may include means for providing documents associated with a user location and indicative of usage by a user or users, a concurrence rater to analyze the documents for usage data of objects in the documents and to generate associated concurrence ratings, and an interface to transmit the concurrence ratings to a data entry device. The concurrence rater may further analyze the documents for location data of the objects and generates concurrence ratings, and the concurrence ratings may be at least partially based on how far a location associated with the location data of the object is from the user location. Also, the concurrence ratings may be at least partially based on preferences of a user.

[0014] In another aspect, a communication device includes a transceiver to receive and transmit information. The transmitted information includes information indicative of a user location. The device also includes a vocabulary repository containing information indicative of the probable intended usage of ambiguous information entered by a user of the device, the occurrence data reflecting an association of the user location with the information indicative of the probable intended usage, and a disambiguation engine to resolve the ambiguous information provided to the device to a probable solution by identifying possible solutions and to apply the information indicative of probable intended usage to the possible solutions.

[0015] In one implementation, the system may further include a positioning system used to obtain the information indicative of the user location. Also, a user may input the information indicative of the user location.

[0016] In another implementation, the preferences of a user may determine what information is contained in the vocabulary repository. Also, the indicative information associated with the occurrence data may be eliminated from the vocabulary repository when the occurrence data reaches a certain threshold. The occurrence data may contain data that represents usage practices by members of a demographic group.

Google Phone Patent

Discovered by John from Gas Fires & Electric Fires Galore.

{ 14 comments }