I built a fake Google login because my MVP demo could not wait for the OAuth console
The author created a mock OAuth server called dummyoauth to bypass the time-consuming process of setting up real social login integrations during MVP development. Frustrated by redirect issues and console configurations, they built a local solution to simulate Google and other identity providers for demos and testing. dummyoauth is not meant for production but helps developers maintain flow while iterating on post-login experiences.
- ▪The author built dummyoauth to avoid delays from configuring real OAuth providers like Google and GitHub during MVP development.
- ▪Setting up social login repeatedly for demos led to wasted time and disrupted development flow.
- ▪dummyoauth simulates real OAuth/OIDC providers locally, allowing developers to test login flows without production setup.
- ▪The tool is intended only for development, testing, and demos, not for use in production environments.
- ▪dummyoauth supports common identity providers including Google, GitHub, and generic OIDC profiles.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 62840) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Jayant Raj Singh Posted on May 16 I built a fake Google login because my MVP demo could not wait for the OAuth console #webdev #productivity #startup #sideprojects I did not set out to build an identity product. I set out to ship a thing with a login button, show it to someone, and get a reaction. You know the vibe: scaffold the app on a Saturday, wire up "Sign in with Google" because every boilerplate does, paste the env vars, run it once, record a Loom, send the link.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).