iOS and iPadOS
The primary platform. Health, Face ID, iCloud and the system conventions. Not a port: the place where the app is born.
Independent studio
Trust is not required: what the app does with your data is something you can check yourself. It stays on your device, encrypted, and you can export it whenever you want in a format that opens without us.
One data model, three ways of living in it. Every system has its own conventions and integrations, and a shortcut borrowed from another one shows immediately.
The primary platform. Health, Face ID, iCloud and the system conventions. Not a port: the place where the app is born.
Same identity, different ergonomics. On Mac what counts is windows, keyboard and files; on the wrist it is one gesture and the battery.
Second target, handled by its own rules: Health Connect, Keystore, the Back button. The apps reach Google Play as soon as they hold up in real use.
These are not slogans. They are technical choices that sit inside the apps and show in how they behave.
If an app does not need your data to work, it should not ask for it. No sign-up and no backend piling things up: the device is enough.
Database encrypted on the device, key in the system keychain, backups protected. "Encrypted" is a property you verify with a test, not a marketing line.
Full export in open formats, backups you can read and keep wherever you like. Staying should be a choice, not the result of lock-in.
The privacy policy describes the real architecture, not a reassuring version of it. When the two diverge, the bug is in the policy.
Blood glucose diary. Encrypted database on the device, iCloud backups protected by a key that stays in the keychain, Health integration. Shipping on iPhone, iPad and Apple Watch, then on Android and Wear OS smartwatches with Health Connect.
Coming to the App StoreVoice recorder built so a recording survives a phone call, a crash and a relaunch. Audio encrypted on the device. Shipping on iPhone and Apple Watch, then on Android and Wear OS smartwatches.
In developmentQuestions, collaborations, bug reports: write. The person who wrote the code answers.
[email protected] Nivela support Recordago support
LupiFoundry is the name we publish our software under. There is no company behind it, and the full details of the data controller are in the privacy policies, where the GDPR requires them to be.