Update: After speaking with a number of other developers, including Silvio from Reeder, I’ve decided that the best thing to do is re-enable MobileRSS’s API key. The developers who made MobileRSS have a number of other apps with Read it Later support (on Twitter, iPhone and iPad). I’ve discovered that all of these apps use the same API key so disabling it unfairly affects an enormous number of innocent Read It Later users using the developer‘s other apps.
Ultimately the decision of what app to use/support should be up to the user. While I may have strong opinions when it comes to defending follow developers, I will leave the decision about what apps to use up to you, the user. It seems that this issue has gotten enough attention that I hope users will have enough information to make their own decision.
Thank you all for your support and feedback.
(Now get off the internet and go drink some Eggnog.)
A recent update to the popular MobileRSS application was inappropriate. It appeared to be an almost identical one-to-one clone of another application: Reeder.
Inspiration and imitation are a natural part of competition, especially in a market as tight as news readers. But in this case, I personally felt that MobileRSS went too far. As a solo developer, I rely on app sales to support myself. A lot of other iOS developers do the same, including Reeder. We simply don’t do things like this to each other.
As a result, I have decided to disable MobileRSS’s API key for the time being. This is not an app that I would like ReadItLater to be a part of in its current form.
This is a tough decision because MobileRSS was the 3rd highest news app used by Read It Later users over the last year. Understandably, a lot of you are going to lose functionality that you may have paid for. I do not want to throw all of you under the bus as a result of this decision.
If you have bought MobileRSS and were using it as your main news reader, please drop me a line at email@example.com and I will do my best to find a way to offset the cost for you. (Please include your username)