Veyn Connect · draft v0.1
Let Doyo act in your app, with the user in control.
Veyn Connect is how an app or service tells Doyo what it can do for a Veyn user: get a ride, show a place, open an order. You describe it once in a manifest. Veyn decides when to offer it, what data it gets, and when the user has to confirm.
Draft. This is a design under review, not a live programme. There is no sign-up and no way to submit a connector yet. Nothing here is a commitment, and details will change.
How it works
- A user asks Doyo for something: “book a Grab from home to One Utama”.
- Doyo asks for an action from Veyn's catalog (
ride.request). It never learns how any one app works. - Veyn picks the connectors the user turned on that can do that action where they are, and opens the best one with the details filled in.
- The user checks the details in your app and presses the last button there.
What the first release includes
Two modes
link opens your app or site with the details in the link. web opens your page in a Veyn web view.
Prepare only
Your service always gets the last press from the user. A connector cannot complete a booking, order or payment on its own.
Two trust tiers
T0 Sandbox for testing, then T1 Listed for verified developers.
API and OS-intent modes, connectors that finish a job themselves, and the higher trust tiers are designed but come later (later). A manifest that asks for them is rejected for now.
Principles
- The user stays in control. A connector does nothing until the user turned it on, and they can turn it off at any time.
- Declared, not discovered. Doyo only does what a published manifest declares.
- Least privilege. You receive the inputs of the one action called, never the user's profile.
- Untrusted by default. Nothing a model writes becomes a scheme, host or path in a link.
- Auditable. Every call leaves a record the user can see.
- Veyn is not in the money. Payments stay between the user and your service.