How to read this page
“Automated” means checks in an isolated test environment, not a guarantee for every device. “Not verified” means no suitable direct evidence is recorded here; it does not mean the feature is absent. No native iOS/Android app-store release or independent security certification is claimed.
Current evidence
| Area | Recorded evidence | Limits |
|---|---|---|
| Public introduction | 2026-11-07: automated entry/metadata/asset checks; desktop and 390/320 px previews inspected. | Preview viewport emulation, not physical phones. |
| Workspace saving and recovery | 2026-11-07: recorded Chromium release checks cover note/revision reload, encrypted lock/reload, safety export, full restore and offline reopening. | Controlled fixtures, not a guarantee about a user’s downloaded backup or storage quota. |
| Media and annotations | 2026-11-07: recorded automated/browser checks cover original media preservation, annotation links, search and Markdown edit/reload. | Browser codecs and media sizes differ; physical recording hardware not covered by those checks. |
| Fresh-profile restoration | 2026-11-07: browser UI restored a full-backup serializer fixture into a new isolated profile; PNG/WAV bytes, image region, zero-second bookmark, precise transcript and source link survived reload. | The actual browser-downloaded file was not available for direct inspection in that check. This does not prove a user retained a usable download. |
| Physical iPhone Safari and Chrome | Not verified on physical devices in this review. | Keyboard, rotation, safe areas, microphone, installation and storage behaviour need a physical-device pass. |
| Safari/WebKit desktop | No current successful WebKit run is asserted here. | Installed browser binaries alone do not prove a working or tested runtime. |
| Live cloud sync | Automated simulated-provider conflict and authorization tests are recorded. | Live multi-device Google Drive/Dropbox/OneDrive operation is not verified by a simulated response. |
| Live team collaboration | Automated Yjs convergence, invitation and lifecycle checks are recorded. | Live shared-folder permissions, peer networks and reconnection across real devices remain unverified here. |
| Accessibility | Recorded keyboard and translated Help layout checks; public pages use semantic headings and navigation. | No human screen-reader assessment or formal WCAG conformance audit is claimed. |
Dates describe recorded checks, not continuous monitoring. New browser versions, provider settings and device limitations can change results.
Before depending on NoteTisa
- Write a disposable note, reload and check that it remains.
- Make a backup that includes a small attachment and recording. Restore it in a separate browser profile and inspect the content.
- While online, let the workspace cache fully; then check the same disposable notebook offline.
- If using sync, test a disposable notebook across your devices, including conflicting edits, disconnection and a deletion.
- If using a phone, test typing with its keyboard open, the last item in the Items panel, tool menus, rotation and recovery.
Do not run destructive experiments on your only notebook. Keep an independently retained backup first.