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
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
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.
The text was updated successfully, but these errors were encountered:
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.
To bring Readup back to the web:
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.Jeff:
This one: faadeb7 ?
readup.com/read/slug
so it:Old ideas:
Modifyreadup.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 installedModify the reader to be able to run withinbecause 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.readup.com/read/slug
when the extension is installedThe text was updated successfully, but these errors were encountered: