My book app is coming along, but the codebase getting really complicated. I might change my plans and not make it open source, at least not right away.
Still, the main idea stays the same: build it for myself first and make sure there are multiple ways to own your book data. Most likely, that means things like Nextcloud sync, an API, CSV export...
@rolle from where are you fetching book covers? They look consistent, need it for my now page 😬
@toni_lijic Open Library, Google Books, etc. some added manually.
@rolle For what os is this coming and will it be cross-platform on mobile/desktop? I really like the idea.
@petrimarkkanen I'm currently working on web and iOS. Version 0.0.9.
Key features:
- Reading focus timer for audiobooks, ebooks, and physical books
- Daily and yearly reading goals with detailed statistics
- Full ownership of your data
Coming later:
- Sharing progress on social media (for example, books read per month or year)
- Sharing reviews or even adding ActivityPub support
Basically, this will be a Bookshelf or Margins clone, but more open and web-first.
@rolle Don't be shy about open sourcing, release early, release often!
@pahoittelemme I'm not being shy here, I have over 800 repos on GitHub. But I'm still unsure about this one since developing it already comes with costs, and there are some scope and security concerns I'm still thinking about. SwiftUI and Next.js aren't fully familiar to me either, and I need to revisit the overall strategy for this project. I might go for a freemium model if I ever decide to open it up to a wider audience. We'll see.
If this were just a simple app to set up and deploy, it would be a no-brainer to publish the repo right away. But since it relies on Big Tech services like Supabase, Vercel, Cloudflare, and others, and because the infrastructure and multi-user account management have gotten a bit out of hand, this is where I'm stuck, and chose keep it private at the moment. Everything is in git, just not public. I guess I just can't do anything half-assed 😅
