RSS me my balances!
We’re working on an RSS mechanism to distribute balances and transactions to members. We are currently building it and beta testing it with employees but we’re kinda stuck on exactly how the balances should be delivered.
Option 1: A feed for each account. The title of the feed is “Checking – Balance”, thus every time the balance changes it’ll show up new in the feed reader. The content of the feed would contain the last X transactions with Y days. Algebra, I know. For example the most recent 10 transaction in the last 30 days.
Option 2: One feed for transactions with each addtional transaction becoming a new entry and a second feed that displays balance.
Which would you rather see, #1 or #2? Are we missing a whole other way to do it that could be better?
I like option #1. I think it gives you the most flexibility with your feed reader.
Great idea! I’m really interested to see how it comes out.
I may not be the target market, but I would love to see functionality like option 2, possibly with a third, consolidated feed. Especially if there is enough meta-data in the transactional feed – one could come up with some pretty neat mash-ups. It could also make it really easy to implement highly customized personal mobile alerts (especially with a real time host).
With enough traction on the format (and enough meta-data) and some creative developers we could see near real time updating of the likes of Wesabe and Mint, using Y! Pipes to create a feed Google Calendar could consume to see transaction and balance information on the calendar, cool business expense reporting applications that simplify and speed up expense reports
Even more far out cray things using feed manipulation tools like Y! Pipes – I’m thinking automatic check ins to Brightkite based on merchant location, Google Maps with locations/heatmaps of spending (fun for travelers!) and I’m sure there are tons of things people would think up with feeds of transactional data.
Good luck, sounds like fun!
Both ideas sound good to me, but I would also look at how that data can be securely fed into Mint, Wesabe, Jwambalooster, etc.