Ways to integrate
Four ways to put Doshi in front of your members. They differ in where Doshi runs and who signs the member in. Pick one, and its guide takes you from your console to live.
IframeOur page, framed in yours. We ship updates, and members signed in to your app go straight in.WebviewOur page, in a webview inside your iOS or Android app. We ship updates, as with the iframe.SDKOur code, bundled into your web page or app. It changes only when you upgrade.Hosted linkA link to our page. Nothing to build, and members sign in to Doshi.
| Method | Where it runs | Sign-in | Pick this when |
|---|---|---|---|
| Iframe | Our page inside yours | Your app vouches for them | You accept framing a live page |
| Webview | Our page, in a webview in your iOS or Android app | Your app vouches for them | Your app is native, and you accept loading a live page |
| SDK | Your web page or app, our code bundled in (Learn only) | Your app vouches for them | Your policy forbids live third-party pages |
| Hosted link | Our page, at an address of your own (not live yet) | Members sign in to Doshi | You want no integration work |
Iframe or SDK
Section titled “Iframe or SDK”Both sign members in the same way. They differ in what they show.
- The iframe shows the whole Doshi experience: Ask, Learn and My plans. It loads a page we serve and update. Your page frames it and answers its token requests. We ship fixes without you doing anything.
- The SDK shows Learn only. It is a package you install, review and pin. It runs on your page, in a shadow root, and changes only when you upgrade. Each release is signed and checksummed so your security team can verify it.
For your security review
Section titled “For your security review”- How sign-in works: how your app vouches for a member with no shared secret.
- Releases and verification: how to check an SDK release before you install it.
- What we deliberately don’t do: what the sign-in standard leaves out, and why.
- Environments: why a Test key can never mint a Live member.