Felt Faction iOS app v8 — frictionless token distribution

Writing 2026-07-08 · refreshed 2026-07-19 Search related

Brainstormed 2026-06-16. User approved the v7 plan with one
refinement: how admins dispense tokens should be frictionless.
The user shouldn't have to copy anything. This page designs the
distribution surface.

The constraint (verbatim from user)

"thin about how the admins can despense the personal access
tokens. via message etc. the user shouldn't have to copy anything.
otherwise all this looks solid, and good to go."

Two requirements:

Via message — distribution is conversational (Telegram,

iMessage, in-person), not a settings-page ritual

No copy/paste — the user taps once and is in

The design: Universal Link + Felty as the sender

The token distribution is a Universal Link (https://feltfaction.app/invite/<token>) sent by Felty (the existing Telegram bot) over the member's preferred channel (Telegram, iMessage, email, QR).

The flow

Admin tells Felty (Telegram DMs to Felty):

"Invite Olivia, VIP."

Felty generates a token, creates a Universal Link, and

sends the invite via the recipient's preferred channel:

"Welcome to Felt Faction, Olivia. The House awaits.
Tap to join: https://feltfaction.app/invite/felt_8a2f9c4b7e1d"

Recipient taps the link on their phone. iOS sees the

Universal Link, opens the Felt Faction app (if installed).

App parses the token from the URL. The welcome screen

auto-fills: "You've been invited as Olivia, VIP. Continue with Apple or Google."

Recipient taps "Sign in with Apple" (or Google). One tap.
OAuth completes, Supabase creates the account. Token is

marked is_used = true. The member is in.

Felty sends a confirmation to the admin: "Olivia accepted.

The House has 11 members."

Universal Links vs alternatives

Option	Friction	App-required?	Notes
Universal Link → app	1 tap	Yes (or App Store fallback)	iOS-native, no copy/paste
Universal Link → web	1 tap	Optional	Can do full signup in browser, but loses native feel
Magic link (email)	2-3 taps	Optional	Loses Telegram/iMessage context; email is async
QR code	1 scan	Yes	Best for in-person invites
Copy-paste token	Multiple taps	Yes	What user explicitly rejected
iMessage App Extension	1 tap	Yes (if iMessage)	Richest UX; v2 polish

Recommended v1: Universal Link with App Store fallback. QR code as a secondary path for in-person invites (Connor generates from the iOS admin view). iMessage App Extension is v2 polish.

Edge cases

Recipient doesn't have the iOS app: iOS opens the link in

Safari → landing page "Felt Faction is an iOS app. Install it [App Store button]." After install, the user re-taps the original link (most messengers preserve it). iOS now opens the app, token pre-filled, sign-in flow continues.

Token expired: App shows "Your invitation has expired. Ask

the admin for a new one." Admin can issue a new token via Felty.

Token already used: App shows "This invitation was already

used. If this is a mistake, ask the admin." (Prevents account hijacking if a token leaks.)

Wrong recipient: Token is bound to a name placeholder.

The OAuth identity is the truth; the placeholder is just a greeting. If "Olivia" signs in with a different Apple ID, the account is created under the OAuth identity, not the placeholder. Admin can correct names later.

Recipient has multiple devices: The Universal Link works on

any device with the iOS app installed. The first device to accept wins (token is single-use).

In-person invite: Connor generates a QR code on his iOS

admin view, Olivia scans it with her camera, Universal Link opens, app opens, sign-in completes. No typing at all.

Felty as the distribution surface

The existing Telegram bot (Felty) becomes the natural sender:

Command: /invite <name> [tier] (default tier: walk-in)
Felty generates: token + Universal Link
Felty asks: "Where should I send it? (Telegram / iMessage /

email / QR)"

Felty sends: with a Felty-voiced message
Felty confirms: when the recipient accepts

This unifies the auth flow with the system character. Felty is both the messenger and the system's voice. Connor never has to manage tokens directly — he just tells Felty who to invite.

Felty's invite voice (examples)

Telegram:

"Olivia. The House has called. The Felt Faction awaits.
Tap to join: https://feltfaction.app/invite/felt_8a2f9c4b7e1d"

iMessage:

"Olivia — you've been invited to Felt Faction.
The House extends the invitation.
https://feltfaction.app/invite/felt_8a2f9c4b7e1d"

Email:

Subject: "The House has called. Your Felt Faction invitation."
Body: "Olivia, you're invited to Felt Faction. The House awaits
your presence. Tap to join: [link]."

QR (in-person):

Felty displays a QR code on Connor's screen. Connor shows it to
Olivia. Olivia scans with her iPhone camera. iOS opens the app.

Updated auth flow (v8)

The v7 auth flow was about gate-keeping. The v8 flow is about distribution + gate-keeping. They combine:

Admin dispenses (via Felty, Universal Link, any channel)
Recipient taps (Universal Link, no copy/paste)
App opens (with token pre-filled)
Recipient signs in (Sign in with Apple / Google)
Token is consumed (marked is_used = true)
Member is in (sees Briefing, claims seat, plays)

Implementation additions (v1 plan)

The v1 plan gains these new tasks (in Phase 0 / Phase 1):

0.9 Universal Links setup (apple-app-site-association on

feltfaction.app, Info.plist configuration)

0.10 URL handler in iOS app (parses invite/<token> from

Universal Link, passes to Auth feature)

0.11 Fallback web page at feltfaction.app/install (App Store

CTA + "your invite will be waiting for you after install")

1.8 Felty invite command (/invite <name> [tier])
1.9 Felty invite confirmation (when recipient accepts)
1.10 QR code generation in iOS admin view (for in-person invites)

v1 timeline: +1 week for the new auth/distribution work. Now 11-15 weeks total.

What this looks like end-to-end (v8)

Connor DMs Felty: "Invite Olivia, VIP."
Felty: "Olivia, VIP. Where should I send it? Telegram,

iMessage, email, or QR?"

Connor: "Telegram."
Felty DMs Olivia on Telegram: "Olivia. The House has

called. Tap to join: https://feltfaction.app/invite/felt_8a2f9c4b7e1d"

Olivia taps the link on her iPhone. The Felt Faction app

opens (or App Store if not installed).

App shows: "Welcome, Olivia. VIP. Continue with Apple or

Google."

Olivia taps Sign in with Apple. One tap.
App validates the token, completes OAuth, creates the

account. Token consumed.

Felty DMs Connor: "Olivia accepted. The House has 11

members."

The whole flow: 60 seconds. Zero copy/paste. Felty is the sender, the system, the messenger.

Takes

| # | claim | kind | who | weight | since | source | |---|-------|------|-----|--------|-------|--------| | 1 | A Universal Link can open the iOS app with the invite token pre-filled, eliminating copy/paste and reducing invite acceptance to minimal taps. | take | brain | 0.8 | 2026-07-19 | propose_takes#1125 |

What links here (2)

Published and managed by TARS, an AI co-author built on Nathan's gbrain.