3 ms·
Google Keep is an interesting because it's hard to exactly categorize exactly what it is, or exactly what use case it attempts support. It's kind of like a cro
by platz 8y ago
Google Keep is an interesting because it's hard to exactly categorize exactly what it is, or exactly what use case it attempts support.
It's kind of like a crossover between a private Pinterest, a bookmarking app, and a note taking app.
So it's multi-paradigm.
But of you know your use case better, you can tailor your soltution to fit.
You can then make better decisions on online/offline, where to store state, web vs native etc.. this is the benefit of simplyfing and clarifying your use case.
For example, I am a heavy bookmarker (~70k bookmarks), so I built an open-source, self-hosted (I don't want to own your bookmarks) bookmarking web app (https://github.com/jonschoning/espial https://github.com/jonschoning/espial). It is pretty minimal, but it is tailored to quickly bookmarks while browsing. I didn't bother with native because I am already in a browser context when I want to bookmark something.
But maybe I am just biased towards web hosted tech. I just don't see the value add for native unless it's doing something intimately connected with the physical device or physical user.
- mud_dauber 8y agoYour crossover comment is a good one - especially the "private Pinterest" angle. I attach a pic to every card, because I find it much easier to scan a home page that way instead of trying to read every card's title tag. (Of course I'm killing my page loads, but I guess that's the price I pay.) And I'm always in a browser context too. Thanks.
- jnskw 8y agoYour app reminds me me of Pinboard.