←back to thread

1222 points phantomathkg | 3 comments | | HN request time: 0.001s | source
Show context
randomor ◴[] No.44065611[source]
Wow, after Instapaper went back to indie from Pinterest[1] and Omnivore closing last year this is no longer surprising. This is also proof that read-it-later app as a category is not sustainable as a venture / company backed service.

This is also a category of app that I believe could be better served by local-first native apps. As there is no reason why a server has to be requirement to enjoy the full service. Your computer is fully capable of interacting with these webpages directly....

On Apple ecosystem, there are few alternatives one can migrate to. I also created an app that target this category (and more) called DoubleMemory: https://doublememory.com that has a few different takes as well:

- no registration needed (icloud sync)

- no extension required (just double command + c)

- launches from menu bar as a launcher, in a stunning Pinterest-style waterfall grid

It's all free to use with no limits, as i'm still working on paid features. I'll work on a pocket importer for these who are interested in migrating.

^[1]: https://blog.instapaper.com/post/175953870856

replies(6): >>44065715 #>>44066095 #>>44067151 #>>44067888 #>>44068649 #>>44069945 #
1. podgietaru ◴[] No.44065715[source]
I actually don't necessarily think that's true - As someone that has a bit of a background with the codebase of Omnivore I think the thing that killed that wasn't necessarily the business model (let's be real, they didn't even offer a premium tier.)

I think it was the introduction of features that required an unnecessary amount of processing power. Namely, RSS feeds. Their RSS implementation parsed every new webpage - a large percentage of which would never actually be read.

They hosted on Google Cloud using things like Cloud Functions. A good proportion of articles were parsed using Puppeteer, when a cheaper shorter running HTTP Request would have sufficed. The PDF viewer they used cost an arm and a leg.

None of this is to shit on the legacy of Omnivore, because I think with the team they had they built an incredible product. But I think there was a lot that could have been done to reduce monthly costs, and that there could have been more effort to monetise.

I paid for Pocket (without using premium features), and I donated to Omnivore, but the thing is ... I happened across their community whilst doing / building something else. I wouldn't have known donating / subscribing were even an option if I didn't. I'm sure I'm not the only kind of person who subscribes purely based on the fact I get value from the software.

I'd like to believe there's a viable business model around these sort of things. And honestly, a much less ethical version of me says that there absolutely is when it comes to Data. I don't think it'll ever be mega profitable, but sustainable? Sure. The Omnivore team was like 2 devs and open source contributors. I believe you could get to a point where it'd be able to sustain that team.

replies(2): >>44066066 #>>44069051 #
2. randomor ◴[] No.44066066[source]
You are right. The architecture is just creating burdens and frictions to sustain the business if mostly relies on freemium user expansion. This is especially attractive to VC backed companies as they sometimes are judged by their growth when they are pre-revenue. And growth with free users is like a poisonous apple, that looks appealing but only accelerate the burning of your cash pile. To the point that it's afraid of charge money that may impact their main growth metrics.

I do believe apps like ReadWise that charges a subscription will have a more likelihood of surviving. Or Omnivore if it's less aggressive in expanding to compute-heavy features without charging.

My main point is, this is a category that's better served by local-first architecture, on Apple ecosystem, you also have the added benefit of having icloud sync for free.

3. kimberli ◴[] No.44069051[source]
I loved using Omnivore, and I've found so far in building https://curi.ooo that you can actually do a lot of the legwork in rendering webpages client-side (even on mobile) so that the server-side processing is just used to simplify the HTML. Obviously I'm nowhere near Omnivore's scale but so far costs have been extremely manageable.