You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read mostly on my phone and iPad Mini, but the reading experience on my old & tiny Kindle is still better. Especially in daylight, where the LED screens require high brightness and still produce glare and weird uneven contrast at different viewing angles.
There exist tools to send articles to your Kindle, but of course, I want Readup to track my reading across platforms, and make my Kindle article reading tap into the Readup social layer.
How this could work
My Kindle is from 2017, but it does have a web browser. I suggest a super bare-bones proof-of-concept Kindle Readup web app, intended purely for reading, as a sidecar to the current app & web app.
It has a new frontend created from scratch, initially only allowing email log-in, a view of My Reads, and a simple reader implementation. What's left out initially: commenting, the AOTD listing, settings, ... It would communicate with the existing ASP.NET API (& hence, the existing db).
The new reader view would integrate the existing JS article parser & tracker. It would crucially depend on a article proxy to get article content. We haven't tried this out yet, but the new reader web extension already paved part of the way to get there (the new extension kind of proxies article requests already). This poses limitations, the most serious one being that the user has to procure/host their own proxy, since we won't share one publicly for legal reasons.
This means that the app would initially only be accessible for technically-inclined users. We could make it easy for people to host their own proxy, using a guide, or one-click VPS/docker install. Some inspiration for guides can be found with Discourse or Chatwoot
I'm sure the (2017) Kindle Web Browser will pose some technical challenges. It would be an interesting task to see what web features are supported on it. I'm fairly certain it supports HTML better than JS, so using a largely server-rendered framework would make sense. With my predominant JS experience and Readup's existing TS/React code, I'm thinking of Deno Fresh, which tries to minimize JS but with TS & Preact. Alternatively: Next.js, Remix, or SvelteKit.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Motivation
I read mostly on my phone and iPad Mini, but the reading experience on my old & tiny Kindle is still better. Especially in daylight, where the LED screens require high brightness and still produce glare and weird uneven contrast at different viewing angles.
There exist tools to send articles to your Kindle, but of course, I want Readup to track my reading across platforms, and make my Kindle article reading tap into the Readup social layer.
How this could work
My Kindle is from 2017, but it does have a web browser. I suggest a super bare-bones proof-of-concept Kindle Readup web app, intended purely for reading, as a sidecar to the current app & web app.
It has a new frontend created from scratch, initially only allowing email log-in, a view of My Reads, and a simple reader implementation. What's left out initially: commenting, the AOTD listing, settings, ... It would communicate with the existing ASP.NET API (& hence, the existing db).
The new reader view would integrate the existing JS article parser & tracker. It would crucially depend on a article proxy to get article content. We haven't tried this out yet, but the new reader web extension already paved part of the way to get there (the new extension kind of proxies article requests already). This poses limitations, the most serious one being that the user has to procure/host their own proxy, since we won't share one publicly for legal reasons.
This means that the app would initially only be accessible for technically-inclined users. We could make it easy for people to host their own proxy, using a guide, or one-click VPS/docker install. Some inspiration for guides can be found with Discourse or Chatwoot
I'm sure the (2017) Kindle Web Browser will pose some technical challenges. It would be an interesting task to see what web features are supported on it. I'm fairly certain it supports HTML better than JS, so using a largely server-rendered framework would make sense. With my predominant JS experience and Readup's existing TS/React code, I'm thinking of Deno Fresh, which tries to minimize JS but with TS & Preact. Alternatively: Next.js, Remix, or SvelteKit.
Beta Was this translation helpful? Give feedback.
All reactions