What you've built looks nice - I have a few questions?
- why would I use this over the standard client? IOW what's it buy me?
- its not clear to me if you're targetting mobile or desktop with this client. can you clarify?
Hmmm, well first I would say there are several excellent clients, and I suspect there will be more appearing as greader apocalypse approaches
I created DripDripDrop because:
1. I enjoy writing software
2. I wanted to marry the speed of Newsbeuter with the convenience of a browser app.
Before TTRSS I was using Newsbeuter and liked a lot of things about it. It's very fast for reading feeds but one of the problems with console apps is they don't scale text nearly was well as browsers do. Newsbeuter also isn't that network friendly with how it pulls feeds. After I started doing network traces I realized it was always pulling down the full feeds from TTRSS instead of just unread.... In my case that was around 24MB of data on the wire for ~400 feeds. I modified the server to sniff for Newsbeuter and add the unread_only flag
3. DripDripDrop presents a very clean, simple interface (some would say too clean). The keyboard shortcuts make it really fast and I added a few small features I find missing in other clients - one example is if I mark a feed read, don't present me with a blank page saying "No articles to show". If you know that take me back to the list of feeds without requiring more actions from me.
In the end I think more choices are better.
In terms of what I'm targeting. This first release targets the desktop browser first and mobile 2nd. I just need to spend some more time with the UI on mobile. It works on mobile now but it isn't as nice looking as it should be and the keyboard shortcuts don't work there