Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring Readup back to the web #50

Open
6 of 9 tasks
th0rgall opened this issue May 19, 2022 · 0 comments
Open
6 of 9 tasks

Bring Readup back to the web #50

th0rgall opened this issue May 19, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@th0rgall
Copy link
Member

th0rgall commented May 19, 2022

See here for the proof-of-concept that shows that we can leverage only a manifest v3 web extension to gain feature parity with the desktop apps.

  • Test & design this POC also for Firefox, Safari, and Edge. It needs to work on all platforms if it is to replace the current desktop apps.

To bring Readup back to the web:

  • Bring back wide app support for BrowserRoot: this can be a near-duplicate of the current responsive AppRoot, save things like a back button etc. Check the commits where we removed the support for BrowserRoot as a Readup app UI component.
  • Allow account creation & signing in via the web again
  • Create a new manifest v3 web extension that includes:
    • A service worker that can act as a proxy for cookie-less HTTP requests, mimicking the current HTTP requester from the desktop/iOSapp
    • x] The old web-extension's (pre-desktop-release) capability of bundling and injecting the reader into a web page
      Jeff:

      the best way to implement it would be to create a new web branch from the last version of the old extension (which I believe should still work!) and just change the manifest permissions and implement the fetching with that architecture, potentially using a new local extension reader page to host the existing reader view

This one: faadeb7 ?

  • Modify readup.com/read/slug so it:
    • when the extension is not installed: shows install instructions and a link to the actual site
    • when the extension is installed: redirects you to that article in the local reader web extension page.
  • Modify the onboarding instruction to reflect the way things work now.
  • Remove support for the apps: don't deep-link to the app on desktops anymore.
  • Look into making Readup a PWA, so we can have the focused quality of a window/windows without URL bar & tabs, like the desktop apps currently.

Old ideas:

  • Modify readup.com/read/slug so it can request article HTML via the extension, and show install instructions and a link to the actual site when it is not installed
  • Modify the reader to be able to run within readup.com/read/slug when the extension is installed because of how the UI/reader interface currently works with message-passing in iOS and the Desktop extensions, it's probably easier to run the reader in a separate window/local chrome-extension page at first and use the same interface.
@th0rgall th0rgall added the enhancement New feature or request label May 31, 2022
@th0rgall th0rgall self-assigned this Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Progress
Development

No branches or pull requests

1 participant