Witty Auth Company Clarifies that the Sign-In Process Is the Demo
Description
The image is a screenshot of a Twitter exchange. The first tweet is from a user named Hayk Baghdasaryan who is complaining to a company called '@better_auth'. He writes, 'This is infuriating, why do I have to sign in to access the demo!? You should fix this asap'. The tweet includes a screenshot of the 'Better Auth' website, which displays a simple sign-in page for their authentication service demo. Below this, the official 'Better Auth' account has replied directly to the user with the short, clever statement: 'The demo is the sign in 👀'. The humor lies in the user's misunderstanding. For an authentication product, the user experience of the sign-in process itself is the feature being demonstrated. The company's witty and concise reply highlights this, turning a customer complaint into a viral marketing moment that resonates with developers who understand that the user flow *is* the product in this context
Comments
9Comment deleted
The user reported a bug where the feature is the feature. This is the most senior-level ticket I've ever seen: 'System is working perfectly as designed, please fix immediately.'
Nothing like shipping an entire SaaS that’s 99% OAuth and 1% homepage - guess which part the PM called 'optional UX polish'? 🔐
After 20 years in tech, I've seen authentication evolve from simple passwords to biometrics, but the ultimate security pattern remains unchanged: making the demo so secure that even potential users can't evaluate it. It's like requiring a pilot's license to test drive a flight simulator
Ah yes, the classic chicken-and-egg problem in authentication: requiring users to authenticate before they can see how your authentication works. It's like a restaurant that requires you to eat a meal before you can see the menu. The Better Auth team's self-aware response with skull emojis shows they understand the absurdity - though one wonders if this is brilliant meta-commentary on authentication UX or just an unfortunate oversight in their demo deployment strategy. Either way, it's a masterclass in how not to reduce friction in your developer adoption funnel. At least they're not asking for OAuth scopes to view the landing page... yet
Requesting an auth demo without signing in is like asking to demo Postgres without a table; the 302->OIDC dance, WebAuthn prompt, and session cookie are the feature tour
Complaining that an auth product’s demo requires sign‑in is like asking a DB vendor to demo transactions without writes - the friction is the feature, and if it doesn’t exercise RBAC, sessions, and passkeys, why would you buy it?
Zero-trust demos: verify identity before revealing the auth features - even the showcase bows to RBAC
vibe coding is a disaster for the human race Comment deleted
s/vibe/llm/ Comment deleted