Problem
Current onboarding is too complex for non-technical users:
Manual copy/paste of tls://…?password=…
User must understand “own peer”
High error rate
Onboarding fails before communication starts
This limits real-world adoption and discourages decentralization.
Goal
Provide one-click / one-scan onboarding without requiring users to understand network concepts.
Proposed Solution
- Deep Link / App Link Support (Android)
Support a custom URI scheme or HTTPS App Links, for example:
mimir://join?
peer=tls://jupiter.example.org:64131
&password=XXXX
&invite=YYYY
or:
https://go.mimir.im/join?peer=...&password=...
Expected behavior:
App opens automatically
Peer is added
Invitation is accepted
No manual configuration required
- QR Code Import (Fallback)
Allow importing peer configuration via QR code containing:
URI (tls://…)
or a JSON payload
Example:
{
"peer": "tls://jupiter.example.org:64131",
"password": "XXXX"
}
Security Considerations
User action is explicit (link click / QR scan)
Comparable to invite links used by Signal, Matrix, DeltaChat
Optional: expiring or one-time tokens
Benefits
Significantly lower onboarding friction
Enables non-technical users
Reduces support overhead
No loss of decentralization or user control
Summary
Decentralization can be complex.
Onboarding should not be.
Without deep-link onboarding, Mimir remains a tool for advanced users rather than a practical communication app.
Problem
Current onboarding is too complex for non-technical users:
Manual copy/paste of tls://…?password=…
User must understand “own peer”
High error rate
Onboarding fails before communication starts
This limits real-world adoption and discourages decentralization.
Goal
Provide one-click / one-scan onboarding without requiring users to understand network concepts.
Proposed Solution
Support a custom URI scheme or HTTPS App Links, for example:
mimir://join?
peer=tls://jupiter.example.org:64131
&password=XXXX
&invite=YYYY
or:
https://go.mimir.im/join?peer=...&password=...
Expected behavior:
App opens automatically
Peer is added
Invitation is accepted
No manual configuration required
Allow importing peer configuration via QR code containing:
URI (tls://…)
or a JSON payload
Example:
{
"peer": "tls://jupiter.example.org:64131",
"password": "XXXX"
}
Security Considerations
User action is explicit (link click / QR scan)
Comparable to invite links used by Signal, Matrix, DeltaChat
Optional: expiring or one-time tokens
Benefits
Significantly lower onboarding friction
Enables non-technical users
Reduces support overhead
No loss of decentralization or user control
Summary
Without deep-link onboarding, Mimir remains a tool for advanced users rather than a practical communication app.