A reading-note workflow worth testing: keep the excerpt and your interpretation separate. Capture a short passage with its source, then write one sentence about why it matters. Put related ideas into a mind map, and revisit the original passage before turning a note into a claim. This keeps a memorable quote from becoming a conclusion without context. This is the workflow behind MindNote, the cross-platform reading app I am building. It connects book excerpts, personal notes and mind maps, with a route back to the source and sync across Windows, macOS, iOS and Android. The product and reading workflow are here: https://www.mindnote.site/ How do you keep your own interpretation distinguishable from an author’s words?
A café changes the price of an espresso. Where does the old price survive? Usually in the menu PDF linked from Maps, even after someone updates the counter menu. For Menu-on we keep the destination stable: the QR code on the table and the link in the café’s profile open the same menu. The owner sends us the change; we edit the dish without replacing either link. One useful test: scan yesterday’s printed code after changing a price, then switch languages and check the same dish. The menu and editor are shown here: https://menu-on.com/main?lang=en
Test the file name in the download dialog Download an image from the preview and read its name in the save dialog. Check the folder where it lands, too. A name that makes sense in the export list can still turn into something generic on disk. Use two versions of the same image for the test. A suffix such as print proof or small preview should let someone pick the right file from the download folder without opening both. If the suffix goes missing, include the filename you actually received when you report the issue.
