SMeetSMeet Mini Apps · SDK v1
A web app in a SMeet window, made by the bot’s author.
A mini app is a web page connected to a bot: a form, a service desk, a small tool. It opens from the bot’s profile, a button in the chat or a link, signs the person in through SMeet when they agree, and sends the result to the bot. The page and its server are the author’s; the window, the consent and the confirmation are SMeet’s.
The catalog lists the mini apps published in SMeet’s public space. To make one, start with a bot in My bots; sign in first.
/start
Hi! Fill in the guest form, it takes a minute. Your answers stay on your device until you send them.
Thank you, the form is received. We will write here when your place is confirmed.
For people
You see what the app gets, every time.
A mini app opens only after you agree, and each time SMeet says what the author will receive. A result goes to the bot only after you confirm it.
- Open it from the bot’s profile, from a button under the bot’s message, or from a link someone shared.
- The author gets your SMeet user ID and interface language, and your display name only if the app asks for it. Never your e-mail, phone number, contacts or chats.
- The window’s menu has About the author, Report, Revoke access and Block bot, and SMeet’s own Close always works.
- A test version says so in the window: SMeet has not reviewed it.
Before the app opens
What the consent screen lists, in the app’s own words. Open and Cancel come after it.
For authors
Your page, your server, SMeet’s window.
You need a bot in SMeet and a page on your own HTTPS address. SMeet handles the window, the consent, the sign-in and the confirmation before a result reaches your bot.
- Create a botIn SMeet BotFather (
/newbot) or in My bots, as for any bot. - Create the mini appSend
/miniappto SMeet BotFather or open Mini app on the bot’s page in My bots. Accept the rules for authors, then give a name, a description, an age rating and the addresses of the production and test versions. - Confirm your domainServe
/.well-known/smeet-mini-app.txtwith the app’s token, and let only SMeet frame your pages withframe-ancestors. - Connect the SDK and sign inThe page loads the SDK and asks SMeet to sign the person in. Your server exchanges the one-time code with its key for a session, and checks that session before every protected step.
- Test, then publishInvite testers to the test version, send the app for review, and publish it once it is approved.
The catalog
Every published mini app of the public space, on one page.
The catalog shows the name, description, age rating and author of each app, with a link that opens it in SMeet. Apps of organisations stay inside the organisation and are not listed.
SMeet’s own apps
A form you fill in a SMeet window and send to the bot, which answers in the chat.
Requests with a file and their status, for the members of SMeet’s demo organisation.
Where it works
Web, iOS and macOS
The SMeet web app, and SMeet for iOS and macOS from the version that brings mini apps.
Android later
Support for Android comes in a later release. There, and in older versions of the apps, a mini app button does not open.
Not in version 1
No payments
Mini apps do not sell anything and do not link to purchases.
No device access
No camera, microphone or location for apps of other authors; only a file the person chooses.
Safety
A mini app gets what the person allows, and nothing more.
SMeet checks access on every launch, on every sign-in and on every result sent to a bot. Nothing depends on an app behaving well.
The rules for authors- Consent before every launchThe consent screen is SMeet’s own, and the author’s page cannot draw over it or press its buttons.
- Confirmation before sendingSMeet shows what goes to the bot and sends it only after the person confirms.
- Confirmed domainsAn app opens only at the HTTPS addresses its author confirmed, and only inside SMeet.
- Short sessionsThe sign-in code works once and briefly. The session ends when the window closes, or when the person revokes access or blocks the bot.
- Review and reportsApps of the public space are reviewed before they are published. SMeet administrators review reports and can block an app or every app of its author.
- The organisation decidesAn organisation turns creating and running mini apps on or off for its own space, and approves its own apps.
Documentation
For authors, in English and Russian.
The SDK, the sign-in, your server, publishing and the rules for authors. Reading it needs no account. Prefer Russian? Документация на русском.
Questions and answers
What people ask before they open one.
What does the author of a mini app receive?
Your SMeet user ID and the language of your interface, and your display name if the app asks for it. Loading the app shows your IP address and device information to the author’s server, as any website does. Never your e-mail address, phone number, contacts or chats.
Do I have to agree every time?
Yes. Before every launch SMeet shows the app, its author and what it receives, and nothing reaches the author until you press Open. A result goes to the bot only after you confirm it.
Can a mini app use my camera, microphone or location?
No. A mini app of another author gets no access to the camera, the microphone or your location. The one device feature it has is a file you choose yourself.
How do I stop a mini app?
Close its window. Its menu also has Revoke access, which ends what the author got from you, Block bot, and Report, which sends the app to SMeet administrators.
Where does a mini app run?
On its author’s server, at an HTTPS address the author has confirmed to SMeet. Only SMeet’s own apps run on messenger.scrile.com.
Who can publish a mini app?
During the pilot, authors SMeet has let in. An app of the public space is reviewed by SMeet before it is published; the apps of an organisation are reviewed by its owners and administrators.
Can a mini app sell something?
No. The rules for authors forbid selling digital goods, subscriptions and paid features, and links to such purchases.
Is it compatible with Telegram Mini Apps?
No. SMeet has its own SDK and its own sign-in, and Telegram libraries do not work with them. The ideas will feel familiar, though: a page tied to a bot, opened from a button or a link.
Start with a bot, then give it a page.
A bot in SMeet BotFather, a page on your HTTPS address, the SDK and a short exchange on your server. The documentation walks through each step.
“Create a mini app” opens My bots in the SMeet web app. Sign in first, pick a bot, then Mini app.