Bridger is intended to be a universal document and web content analyser and we want to have it play nice with as many file types, applications and platforms as is possible. Of course, not all companies are as open as they perhaps could be so we do our best.
We developed the Bridger user interface specifically for smartphones and it works well on Android and iOS iPhones. We also quickly discovered that it does a pretty good job on the iPad as well and we are also working on supporting desktops - although this may only be possible using Safari or Chrome at this stage.
More news on this soon.
This openness is possible for a little startup company like Six Degrees Of Data because we use a very agile set of technologies. These include HTML5, CSS 3.1, jQuery Mobile and others and we've tried to be as open as is possible. But this only takes us so far.
Take off-line reading applications like Pocket, Readability and the like. Both are excellent apps that I use a lot on my desktop browser and smartphone. Like for millions of others, these apps have become embedded in my daily browsing habits. One problem however is that they really only delay the inevitable. If I'm going to get any value out of the documents I've saved, then I'm going have to read them. And this is where things fall down.
I often never get around to reading this growing pile of stuff sitting waiting for me in Pocket and Readability.
The unfortunate reality is that the virtual world mimics my physical world habits. Just like my bedside table is piled high with books and magazines I want to read - so are my virtual repositories: not just Pocket and Readability, but also email, Zinio, Flipboard, Kindle, iBooks, Instapaper and the like.
Now there are precious few things that I am certain of in life but I know for a fact that I will never read everything that I have squirreled away in these apps!
And that's the motivation behind Bridger. It Bridger continues to develop like I plan, then I can use it to extract the value trapped in these documents. But I digress - because there are speed bumps on my road to document nirvana.
For example, Readability uses some url mapping tricks to do what it does and this currently stops us using Bridger to analyse readability documents. A pity, but we will keep persevering until all avenues are exhausted.
Pocket, on the other hand has been easy to integrate into our work habits and the following short video shows you how Bridger can analyse all the documents saved in your Pocket app: