Chrome
AvailableRight-click a PDF or an image anywhere on the web and open it in the tool you want, with the file already in hand.
Add to ChromePocketDocs away from this website. Everything here does the work in the same place the website does - on your own device - and nothing here asks for an account.
Right-click a PDF or an image anywhere on the web and open it in the tool you want, with the file already in hand.
Add to ChromeManifest V3 with event pages rather than service workers, and its own dialect of the same API. A port in shape, an errand in practice.
Not a store at all: the same bundle converted with Xcode and shipped through the App Store inside a native app.
None of this is finished, and only one of them has been started. It is written down because a plan somebody can read is a plan somebody can argue with.
QR codes, made in the tab you are looking at. Nothing to upload and nothing that expires. Colours, shapes and a logo in the middle, and the picture you approve is the file you download.
Open it
Short links, beside the codes, because a QR usually encodes one. One of the two things here that need a server, and it will say so.
A bookmark manager that keeps the address, the title and what you wrote about it, and then stops. The page is never fetched or stored, and everything comes back out as the bookmarks file every browser has read since 1994. The only one of these that asks for an account.
Simple forms with a link you can hand out. The answers have to land somewhere, which makes this the most infrastructure anything here asks for.
Automation over the rest of these: the three things you always do to a file, done in order, without you there. On the device wherever that is possible.
A password manager. Encrypted before anything moves, which is this promise one step further along - and the slowest to build for exactly that reason.