WristviaWristvia is an independent project maintained by Tomas Norkus. The product name is Wristvia; its public website is wristavia.app. The site explains a development prototype, not a broadly qualified compatibility service.
Who maintains the project
Tomas Norkus maintains Wristvia and is the contact for support and privacy requests at tomasnorkuss@gmail.com. Guides are published by the Wristvia project. The project is independent of Apple, Google and the source apps discussed here.
Guides are compiled from project development records, official platform documentation and assistance from development tools, including AI. Named device observations are separated from software tests; we do not present generated text or artwork as a physical test.
How we test and report results
Physical observations currently come from one Honor Android phone and one Apple Watch Series 11, with the original iPhone pairing retained and Always On off. This is a development setup, not an independent laboratory or a representative sample of Android phones and watches.
- Implemented: a feature exists in source or an installed build. This does not establish its outcome on a device.
- Software checked: a build or automated check passed for the stated slice. Radio, background and source-app behavior can still differ.
- Physically observed: a tester saw or heard the stated outcome, or a device trace established a specific transfer. We record the scope and remaining limits.
- Unresolved: no qualifying result exists, or a failure or ambiguity still needs a fresh test.
Apple accepting a push, the watch saving a receipt, an alert appearing, sound/haptics and a person noticing it are separate events. A source-app command dispatch does not prove a recipient received a reply.
Dates, versions and original evidence
The device report records build baselines, dated results and remaining checks. A new build does not retrospectively reverify an older result. One-record Bluetooth health transfer is not a full import, overnight run or airplane-mode qualification.
Private keys, tokens, registration files, personal notifications and health values stay out of public evidence. Published screenshots label fixtures or synthetic content; generated Concept C product artwork is illustrative. We do not publish a battery-saving percentage, delivery pass rate or broad supported-device claim without matching measurements.
Corrections and changes
Article update dates mark substantive content changes. When newer evidence changes an earlier conclusion, we revise the affected guide and preserve useful historical limits in the test report. Report an inaccurate or unclear statement to tomasnorkuss@gmail.com with its page link and the statement in question.
Production release, real-store billing and general compatibility remain separate qualification work. See availability and pricing status.