The next generation RSS reader concept

The problem

Today, almost all websites have some sort of an RSS feed to keep you informed of their latest news.

On the other hand, users may be overloaded by all sorts of irrelevant information that arise from this trend.

The other part of the problem would be a magazine website with multiple areas of interest.

Such a magazine would report hardware as well as software news, Apple as well as Android information, etc.

But what if we are only interested in part of the information provided by RSS?

The solution

Some of the newest RSS readers started to address the issue by providing filtering options that can be used to filter out words, authors, categories or tags that do not interest you.

Their biggest disadvantage is their learning curve. You need to mark each and every part of each post for tags, authors, categories and words that makes that single post irrelevant to you.

jReader tries to address this problem by:

employing an intelligent algorithms that automatically scans tags, categories, authors and titles of each post for repeating patterns

tags, categories, authors and titles of each post for repeating patterns allowing users to mark a full posting as irrelevant (this is where the algorithm kicks in)

(this is where the algorithm kicks in) at the same time, allowing users to mark parts of the post that are always irrelevant (like a category, author or a tag)

The technology

jReader's ideology comes from the simple fact that everything has already been invented.

It would be a waste of time trying to reinvent the wheel, when we have these technologies coming to help:

Google Feed API , a service which can: read just about any RSS data and generate a valid output from them when possible, serves a cached RSS data via a CDN network - making feed delivery lightning fast

, a service which can: Yahoo! Pipes , serving as a solution for: condensing all user's feeds into one, while passing this data back to jReader 's server for filtering and archival purposes. The server will then expose this data and pass it over to Google Feed API for faster delivery. situations when Google Feed API does not recognize the feed in question (like when user enters Web URL instead of Feed URL)

, serving as a solution for: jQuery JavaScript library , providing an excellent base for: display of feeds data directly on user's device from above-mentioned sources a jQuery Mobile framework used to deliver jReader experience to various mobile platforms

, providing an excellent base for: MySQL database backend , storing: usernames and emails of all "registered" users basic information about user's predefined feeds and all posts

, storing: flat-file storage , used to: store copies of posts, so their snippets can be displayed without putting additional strain to the Google / Yahoo! APIs or the RSS feed itself

, used to:

The concept

Now that we have full technology tree listed, let's have a look at how my imagination puts jReader's internals together:

(also available as MindMap and Wireframe)