HN user
As a feature within our app, probably Q2/Q3 this year; we want to finish backfilling historical books before turning actual notifications on
As an API for you to query yourself for free, not for a while (but on the long-term roadmap!)
we built this "work-level" catalog at Margins [1] -- 12mo+ of work -- book data is the messiest data I've worked with in my 10+ years of building things with data
[1] iOS app to track and discover books: https://apps.apple.com/us/app/id6737528718
:) hmu at paul@margins.app with any questions or feedback!
Margins (https://margins.app/) | iOS (Bay Area-based), Backend/Data/AI (Remote within US) | Full-time
We're building the killer app for books. We launched on Christmas Eve and hit 100k users; now we're hiring:
1) a Bay Area-based iOS Design Engineer 2) a Bay Area-based iOS Engineer 3) a Backend/Data/AI Engineer
to help win an Apple Design Award and build the best catalog of book data in the world, respectively.
If "craftsmanship" and "books" resonates, send a description of some things you've worked on to paul@margins.app
More info: https://margins.app/jobs
We're building the killer app for books
Starting with a native iOS app to to track and discover books [1]
Focusing on notetaking and cozy social this year as we try to grow from 100k to 1m+ users
Margins | [Backend, Data, iOS] | REMOTE (SF Bay Area preferred) | Full-time
We're building a home for readers online, starting with an iOS app to track and discover books: https://margins.app/download
We just went from 0 to 100k users in 2 months, raised a seed, and are now hiring 2-3 more engineers. If "craftsmanship" and "books" resonates, we'd love to chat: paul@margins.app
SwiftUI, TypeScript, some Python, GraphQL, Postgres, Supabase, Vercel
Where are the benchmarks that show <1ms p99 overhead? That seems intense to me.
Check out the OpenLibrary Covers API: https://openlibrary.org/dev/docs/api/covers