Enhancing Page Search Engines

Web search engines can deliver a list of relevant results within milliseconds. We know that the information we are looking for probably hides behind one of these search results, but the problem is how to extract it as quick as possible.  In our previous post we discussed the concept of a page search engine; a tool that basically helps you find information within a given web page.

Your browser's built-in search function is a good example of a page search engine. And it's also probably the only example, at least until browseye came into the picture.

A Page Search Engine: Do you Have to Read Lots of Online Documents?




Modern web search engines have succeeded at solving the underlying technical problems of getting access to an ever-increasing amount of information. Nowadays, we can get search results within milliseconds thanks to web search engines. Unfortunately, this is not the end of the story.

According to a comScore study (see figure below), Internet users spend from 4-5% of their time searching and navigating the Web. That means that around 95% of the time spent on the internet we are basically sitting in front of a web page

 


A Different Way of Developing Browser Extensions

Developing browser extensions can be a daunting task. If you want to release a version of your extension for each major browser in the market, you basically have to develop a different extension for each one of them. Sometimes you'll be able to reuse code (e.g., between Chrome and Safari extensions), and sometimes not (e.g., between Firefox and IE extensions).

Let's present three different ways of developing an extension for different browsers. Each way basically represents a different compromise between the amount of effort you have to put in the development of your extension and the control you get over its functionality. The first two ways are well-known, but I believe the third way is not, so let's compare the three of them.

Developing Browser Extensions: The Fast Way


Developing browser extensions can be a daunting task. If you want to release a version of your extension for each major browser in the market, you basically have to develop a different extension for each one of them. Sometimes you'll be able to reuse code (e.g., between Chrome and Safari extensions), and sometimes not (e.g., between Firefox and IE extensions).


In order to simplify this task you can rely on a cross-browser extension development framework. With this choice you'll be able to release a working extension for all major browsers at the cost of having limited control over what your extension can do. This is what I call the Fast Way of developing a browser extension. You may read about other alternatives here.

Developing Browser Extensions: The Normal Way

Developing browser extensions can be a daunting task. If you want to release a version of your extension for each major browser in the market, you basically have to develop a different extension for each one of them. Sometimes you'll be able to reuse code (e.g., between Chrome and Safari extensions), and sometimes not (e.g., between Firefox and IE extensions).

 If you want to develop browser extensions the way each browser meant you to develop them, then you'll have full control over your extension at the cost of the non negligible effort it will take you to learn each extension development framework. This is what I call the Normal Way of developing a browser extension. You may read about other alternatives here