Built for precision mobile engineering
RYNO exists because testing a deep link meant typing long adb commands, losing test URLs in notes and pushing secrets to Git by mistake. RYNO keeps each request as a file in your repository, sends it to Android and iOS from your Mac, and hosts the data of its company service in France.
Why RYNO exists
Testing a deep link by hand means a long command typed into a terminal, and an & in the URL that the shell of the phone reads as the end of the command. Test URLs end up scattered across notes, Markdown files and scripts nobody shares, and test tokens end up pushed to Git by mistake.
Ryno puts each link in a file your team reviews with the rest of your code, sends it with the escaping done for you, and keeps secrets in local files that Git ignores. The same native tools run underneath: see Ryno next to the adb, simctl and devicectl commands.
Ryno also says what it cannot do. On an iPhone or iPad connected by cable, it sends the link through devicectl and cannot confirm that the device received it, so it reports the link as sent, never as a success. See Send a deep link.
The principles behind RYNO: local-first, Git-native, service data hosted in France
- Local-first
The desktop app needs no account and no network to open a project and send a deep link. Your requests, environments, local secrets and run history stay on your Mac.
- Git-native
The folder on disk is the only source of truth. Each request is a file in the
.rynofolder of your repository, versioned and reviewed like code.- Service data hosted in France
When your company shares a catalog, your pipeline publishes it and the service stores it in France, on OVHcloud. Stripe, Google and Microsoft are subprocessors: see security, GDPR and hosting.
Try Ryno on your Mac
The desktop app is free. When your company needs a shared catalog, the team answers your questions.