I would like to use appflowy to be used as an inventory tool.
I would create a folder structure that corresponds to the house where a certain box is:
basement
shelf 1
box 1
shelf 2
box 2
garage
box 3
Now I would like the ability to create a qr code to the page of the boxes through the share menu (that would copy the qr code as an image to the clipboard, maybe with the page title underneath for identification).
This qr code could then be printed and attached to the box. I would then like to scan the qr code from within the appflowy app and be transported to the relevant page. There I could edit the page, insert pictures and a list of the contents. When I move the box, I can move the page and the link would (allegedly) stay the same.
This function (create and scan qr codes) could also be applied to anything that someone needs to see the content or attached information of in the physical space.
Wow! thats a very well explained use case. Right now I dont think AppFlowy supports this, but I suppose you could use an external QR code generator app that can generate QR codes for AppFlowy page links.
If you self-host appflowy and restrict access to only your accounts, these links will point to the respective appflowy pages which only you can see, if privacy is a concern.
thank you for the reply. You are touching on a subject I haven’t really thought about and this is access control and privacy. This might warrant some more thought.
Right now, using an external QR code generator for the AppFlowy pages does indeed work already.
It seems like the link to a page has a fixed format:
The first alphanumeric string (abcdef12-3456-7890-abcd-1234567890ab) seems to identify the workspace, while the second one (12345678-1234-5678-90ab-1234567890ab) points to the unique id of the page.
Generating this URL into a QR code is a good way to access it in a browser on any device. It would be nice if AppFlowy would make it possible to bypass the external QR generator for convenience purposes, but this is a rather lower priority.
The real feature request would be the ability to scan the code (externally or internally generated) within AppFlowy, so the page opens in the app itself and not in the browser.
A workaround might be to have the browser re-direct every request in the form of the AppFlowy URL to the app, but if this could be handled within the AppFlowy mobile app (or Windows client) that would be preferable.