Friday, December 19, 2008

WordDial 1.0

A company named 'web-publishers' has released a new mobile phone application called 'WordDial,' which is not to be confused with the name of the New Zealand company (WordDial) that operates a vast internet directory comprised of dotcom wordnumber portals. Web-publishers, according to its website, specializes in 'interactive data driven web applications.' But its app for the iPhone does exactly the opposite of what you'd think an app a-la-'WordDial' would do. The downloadable iPhone feature, which costs US$0.99, does the simple task of converting text to a number. Their sample inquiry is
'type your text, eg "1 (800) MY-APPLE" and click the "Get Number" button. WordDial will convert it into a phone number, tap number to dial.'
More, including screen shots, can be found on the 'WordDial' webpage.

What is really needed is the opposite to the WordDial app, a feature such as 'allnum:,' the Google operator developed for its Google Number Search protocol. The allnum feature still works, and if you are ambitious enough you can set your mobile hompage to http://www.466453.com/search?q=allnum%3A and successfully translate just about any NUMERIC inquiry into its WORD equivalent. Visit the link, and add a 'wordnumber' like 262966 and you're provided with a lightning fast link to Amazon.com. Just don't try any word or name that wasn't on the internet in 2000. Why? Well, that's a long story...(that you can read about in our archives).

Labels: , ,

Saturday, January 05, 2008

Give voice-activated directions a rest: use your thumbs

IAC Search & Media, the parent company of ASK.com, announced on Thursday (Jan. 3, 2008) that it has incorporated the voice-activated technology developed by Dial Directions (Dialdirections.com) into ASK.com's mobile directions service. The press release asserts that "voice input is a natural complement to the Ask.com Mobile Directions" portal and is an improvement (over typing on a mobile device) because it 'eliminates typing addresses, which can be slow, error-prone and, in some cases, unsafe.'

Now wait a second. Typing addresses on a mobile device may in fact not be more difficult. If you think of all the hard-to-pronounce street and city names out there, you'd be certain that ASK.com has not 'figured it out' and users will be wasting away minutes speaking s-l-o-w-e-r and s-l-o-w-e-r before eventually giving up. You can be certain that a percentage of the time ASK.com won't recognize peoples' pronunciation of cities or streets in the U.S., for example cities named by the Native American Indians or early Spanish settlers. Try getting directions to or from Wewahitchka, Florida, from ASK mobile's speech-activated directions search engine...just try.

As we blogged about earlier this week, automated voice-based search directories aren't perfect and neither are automated voice-activated directions services. Unless you're using a live person (e.g., ChaCha), text input will always have to be incorporated into any form of mobile search and only the folks at Google have figured out a way to make texting truly fast, easy and simple.

Using Google Number Search technology to type addresses *can be* (if the technology was applied) quick, error-free and quite safe as evidenced by this simple sample query, '10 3696464 787338,' which spells a popular address on your keypad:

http://www.google.com/search?q=allnum%3A10+3696464+787338

Google simply needs to fold-in GNS into Google Maps Mobile and as a result it would be far more accurate, easier to use and safer than ASK.com's voice-activated directions service.

Labels: , ,

Thursday, December 27, 2007

Did you mean...Were you looking for...

It was too good to be true. DigitURL's 'were you looking for' wordnumber translator is not anything like Google Number Search and it appears that DigitURL's webmaster is using a manually created database. We assume they downloaded a list of the most popular 1 million or so websites accessed in Australia (which includes many non-Australian web destinations too). Then they parsed out and translated the SLDs (second level domain; the brand name before the .com or ccTLD) into wordnumbers, sorted the wordnumber-domain pairs, and put the database up on its server. So, when you search using wordnumbers consisting of 2 or more digits via DigitURL, the wordnumber in your search query is being matched against the wordnumber translations for the brands of the top 1 million or so ranked websites based on Australian usage.

How is this not Google Number Search? GNS, first of all, operates in conjunction with a search engine not a database (and it helps that Google operates the top ranked search engine). Second, whereas DigitURL provides shortcuts to a finite number of web destinations, GNS provides the ability to use wordnumbers to substitute for any search term, including phrases and names and so forth, to 'Google' all pages on the internet. There is an infinite number of combinations of wordnumber search terms that will generate meaningful results. GNS accomplishes this with a very high success rate of wordnumber translations. In a nutshell, GNS is Google search but via an 'invented' shorthand for typing search queries. There still is no comparable webservice out there. The only caveat is that GNS is still linked to an outdated lexicon (from about the year 2000).

Creating such a database that DigitURL has put together may be simple enough. Website ranking companies provide free and not-free lists of the top 100k or million most popular sites. The not-free companies also provide ranked lists by geography (country).

The problem with DigitURL's 'were you looking for' script is that it is a limited search tool. By having a database of wordnumber translations for a static - or even updated - ranked list of the top 1 million or so websites, then websites for smaller, upcoming, tech startups will nearly always be inaccessible by DigitURL during their infancy. If one thinks of the target audience of DigitURL, it would make more sense to get a ranked list of top websites for the Y generation or tech sites or of Web 2.0 properties, etc... Many of these web destinations will not be accessible until they reach some threshold of popularity. Many mobile phone users want to be 'better than that.' They want to be on the crest of the wave. Not watching the wave from the beach.

Labels: ,

Wednesday, December 26, 2007

DigitURL takes on short wordnumbers

DigitURL now provides users with a near replica of Google Number Search translation for short wordnumber (numeric) entries. It has done this without the use - so it appears - of a manually created database of urls with their wordnumber translations.

Take for instance the string '222.' DigitURL returns every popular brand associated with that wordnumber. You get ABC. You get BBC. You get CBC (Canada Broadcasting Company). And ALL within 4 keytaps of opening the DigitURL app or bookmarked link. Compare with typing out BBC.com, an incredibly long 14 taps (w/o the dot).

This is precisely the type of search query that, of all available web-services, only Google Number Search could handle (until now). View, for comparison, what results GNS provides for the same search query of '222': http://www.google.com/search?q=num%3A222

What is significant is that both services provide results for short wordnumber strings that are meaningful - the results for 2 or 3 digit wordnumbers are ranked in a similar sort of way that search engines provide. That is a pretty difficult task considering that any 3-digit wordnumber, for instance, could be associated with 27 dotcom domains (more for the numbers 7 and 9 which have four letters assigned to them) - assuming that every LLL.com is regged. The situation gets even more complex when you think of all the other cc TLDs. There is significantly less competition for wordnumbers (including dotcom wordnumbers) that are four or more digits in length. Yet DigitURL does both just fine - most major brands with URLs of a medium to long length are represented by their wordnumber (6977223 is MySpace) and wordnumber search queries for brands with tiny URL lengths go to the popular brands you know.

The problem - and it may be intentional - is that there is a local bias that we're experiencing using DigitURL, which is based in Australia; Jamptap is based in the U.S. A trial of the wordnumbers for the 3 digit domains listed in Alexa's top 100 sites in Australia work perfectly - but those in the U.S. top 100 don't. For instance, several domains (of brands that are 2-3 digits long) in the Australian Alexa top 100 including go.com (#50), NSW (#52), VIC (#65), IGN (#70), qq (#76) and even HI5.com (#85) are represented in the results (assigned with accesskeys) when their wordnumbers are entered. This is not the case with the Alexa U.S. top 100 - the brands of many wordnumbers aren't shown in the results.

This begs the question, is DigitURL positioning itself as an internet company primarily targeting Australian consumers? This was the initial posture of WordDial, which began with a near exclusive New Zealand base of users, and since has been building an international clientelle and user base. Without knowing how DigitURL completes its wordnumber translations, it is difficult to suggest how its results could be improved. It is our assumption that DigitURL's algorithm is linked to a search engine with local bias for Australia - we could be wrong about this. If this was the case, then changing that association to a 'global' search engine would be better - at least if maximizing profits is the goal of their business. Certainly DigitURL could do their own geotargeting based on users' ip addresses and provide search results accordingly.

Update1: DigitURL's algorithm also works on some 4 digit or longer wordnumbers - the algorithm is easier to test (and more impressive) using 2 and 3 digit wordnumbers, of course. We found success with the wordnumbers for nearly every single major brand/website in Australia and also for generic words such as 'match', 'money', 'chat', 'love', 'mobile', 'ymail', and others that aren't mentioned on the Short DigitURL list. In sum, DigitURL has stumbled upon an early-stage all-purpose DNS (DigitURL Number System) made for Australians. What about the rest of us?

Labels: , ,

Friday, October 19, 2007

Great frustrations on an un-shoestring budget

Eric Schmidt of Google at 2007 third-quarter earnings call:

"On the mobile search side, our mobile searches are increasing rapidly compared to a year ago. They are growing more quickly than non-mobile searches. They are still a very small percentage of total searches, which is of great frustration to us...' [Emphasis ours]

Here's the answer to your troubles, Schmidt:



Remember Google Number Search?

Labels: , , ,

Friday, July 14, 2006

Google's trial and error mobile strategy

 
Finally, an article that discusses Google and the future of its mobile strategy.
 
The article states: "Undoubtedly, Google would demur from describing its strategic planning process as 'trial and error'. " 
 
{link no longer works try http://mobile14.com/?p=1783}
 
Google not only has the large user base, assets and so on, but it has Google Number Search. 

Google put GNS on the shelf after realizing that droves of users weren't using it.  Although GNS has accumulated a lot of dust, it is actually ready to launch in a moment's notice.  Google just needs to update the GNS lexicon, which includes search terms that were around in the year 2001.  That'll take about a second or two to fix.  Although I think that GNS was an 'error' in Google Inc's 'trial and error' mobile strategy, it will be a big hit one day.  
 

Labels: ,

Monday, April 17, 2006

Why most emerging mobile search technologies will fail

Microsoft recently announced a new search technology called Photo2Search, which would allow a user to search web databases using cameraphone photos - the search would return relevant results as would a text query.  Another mobile search idea is to install barcode scanning technology on cellular phones so users can 'scan' products while shopping to get instant access to product info. 
 
It is clear that mobile search technology is moving, however it is not moving forward.   Mobile users will soon agree on one golden rule for mobile search - there should be one portal which gives me access to all the information I need.  As of now, Google is the one portal that lives up to that rule on the home computer.  However, searching on a mobile device using Google, or any other portal, is problematic because multi-tapping on a phone keypad is too cumbersome.  There is no one mobile portal or solution that meets the golden rule.   To overcome the keypad problem, Google's competitors are trying to come up with solutions to substitute text input with barcodes, photos, voice, etc...
 
The mobile market has not only developed a bad case of amnesia of Google Number Search, but is headed down the wrong road.  More and more subscriptions are being offered to users by carriers that limit users to a small selection of content. When users are offered search capabilities, the results and efficiency of use are far inferior to what they can get on their computer at home. Shrinking a user's web experience or search capabilities will not work in the long run.  Even predictive text technology, which is becoming ubiqitous as the staple technology of mobile search solutions firms like Jumptap (not related to this blog or its editor), will not survive because it is more so much more demanding than GNS on the user. Although both methods require roughly the same number of keystrokes, T9 requires twice the users' attention and faculties than GNS because it requires simultaneous attention on keypressing AND repetitive (visual) scanning of possible results for each keypress, whereas GNS requires attention only to inputing the query.
 
Google Number Search has the optimal flexibility for mobile search.  It's strength over other mobile search technologies is that it enables the user to locate ANY results on the World Wide Web (Google's index) using a simple interface and set of rules.  GNS allows the user to incorporate very basic and fundamental tools into their mobile search such as the wildcard (asterisk), quotes (number one), spacing (zero) and manual search/override (NUM).
 
One only needs to experiment for oneself the power of number search using allnum: or num: on Google search.
 

Labels: , , , ,