Saturday, May 23, 2009

CONTENT EVERYWHERE - Why RSS readers suck !

It never ceases to amaze me how much free content is available on the internet. Newspaper websites, portals, university classes, company news, online video, consumer product reviews,etc. But even so, getting to the content could still be a laborious and infuriating task -- technical progress was needed to help ...
  1. find and search content (Google)
  2. aggregate content
  3. organize, group and rank content
  4. effectively and conveniently present the content.
To get to this point wasn't easy. Free content is everywhere on the internet but we all needed a "Google" or "Yahoo" to search for it. Then the portals came... but these were ad heavy websites that gave us aggregation at the expense of a dozen flashy ads battling for your eyeballs and forcing us to remember another user login and profile

The real breakthrough in terms of digitally available content on the internet was syndication and the syndication standards that followed. The RSS standard was the major winner in this space and a sleuth of RSS readers (i.e. Google Reader) followed suit but they all suffer the same problem. They force you to seek out, collect and organize your feeds. Who really has the time for that? Some readers (or portals) provided master list of feeds but they usually contained a bunch of stuff you weren't interested in ... and many were never updated to reflect dead links or blogs.

Content is KING -- but you need to give it to the user in an effective, convenient and organized fashion and this is why we created our iHub line of applications. We have "content owners" that intelligently seek out, group and organize our content along with servers that constantly refresh and rebuild our composite feeds.

iHub Theory of Content Evolution

I'm excited -- Our iHubTechnology product is coming out soon. Get Ready To Get Your Geek On because we collected and organized the best tech feeds available today.... hardware, software, hacker, security, coding ... YUMMY!

No comments:

Post a Comment