Announcing the New Feedly Mobile and Welcoming 3 Million Reader Refugees
blog.feedly.com
blog.feedly.com
That leads me to believe they are spying. Because, to repeat myself, why else would they need the extension?
Please pile on additional votes to keep the pressure up.
For what it's worth, they claim they are not monitoring your browsing: http://blog.feedly.com/2008/06/18/feedly-and-privacy/
But you're right, still a good idea to push for the web version regardless.
I've literally been waiting over 2 weeks for 1 OPML file with about 30-40 feeds in it to be imported now.
They really need to step up during this advantageous time for them and spin up more servers to handle imports.
I've been checking in every few days and their import rate seems to be less than a thousand OPML files a day (when I signed up weeks ago, it was around 25000 users ahead of me with OPML files to be imported and I'm still waiting). Not giving me much confidence in their company at this early stage.
They also had some serious UI slowdowns for the first couple of days but it is better now. I've also noticed that the feeds don't update as rapidly, but that will probably improve over time and it's mostly only noticeable when compared directly to Google Reader.
Feedly seems to be doing a good job of balancing the new UI features and focusing on the backend replacement.
Any idea how they will make money in the future?
Bunch of whining free riders. Now I understand why Google dumped you.
If you take out the whining people out of the three million, you still have a pretty good user base. A user base which just might be willing to pay if there's a good service. Heck, I'd pay if there was something significantly better than the free Feedly.
You... you don't understand even the very basics of Google's business model, do you?
Spoiler: 99% of their revenue is not derived from direct user transactions to them.
The key is making sure all the layers in your stack are either commodities or can be self-hosted.
For example, proprietary SaaS/PaaS services - bad. Generic and interchangeable Linux systems - good. You can build on top of the latter knowing that you can switch if the service is killed.
Then, for non-standard components (e.g., the application), you must either host it yourself or make sure you have everything you need (code and data). If you don't have the skills, you can pay someone else to set it up, as long as you don't become hostage to them.
It's not unlike cars - if you want something reliable and durable, you're better off choosing the less comfortable model for which parts are easily sourced.