Junayed

@VoltrexAI Cheers 🙏 things have moved since Tuesday: OAuth shipped, dev profiles + app submission live, and the first OAuth demo app is in prod as of this morning. Catalog's no longer just the test server.

@junayed711 said you'd ship by end of week, shipped early. DM'd you.

Day 9 of building Layzer in public. Said I'd ship the MCP apps directory by end of week. Shipped today. Catalog, one-click install, widgets in chat — working with the test server. Real apps next. #buildinpublic #indiehackers #SaaS #AI

@devhanzo1 Update — shipped dev submission this week. Catalog takes external apps now (I manually review each — stopgap, not the long-term answer). The "what can this actually touch" preview you raised is still the trust gap I haven't closed. Probably next hard problem after supply.

@junayed711 one-click install is the easy half. the hard half with an MCP catalog is trust, people paste a server into their agent and it can read everything. nail a "what can this actually touch" preview at submit time and that's the real unlock, not the install.

Day 11 of building Layzer in public. Up at 4, gym. Twins slept in and napped at lunch — two Layzer windows, rare. Built the dev submission flow. Devs submit MCP apps to the catalog, users install in one click. Demo 👇 #buildinpublic #indiehackers #SaaS #AI

@compileandpush Thanks 🙏 Layzer accounts already support 2FA for email/password logins. For OAuth-connected tools themselves, 2FA is inherited from the provider (Google, GitHub etc.) during the consent flow.

@junayed711 OAuth integration seems robust. Any plans for two-factor auth?

Day 12 of building Layzer in public. Shipped OAuth for MCP apps. Users sign in like "Sign in with Google" — Layzer handles the handshake. No more API keys. Unlocks real apps — Gmail, Linear, GitHub. #buildinpublic #indiehackers #SaaS #AI

@rivestack 💯 "brutal in production once non-devs need to use it" — that's the framing I've been struggling to articulate. Saving this.

@junayed711 OAuth for MCP is exactly the unlock people don't realize they need yet. API keys are fine in dev, brutal in production once non-devs need to use it

Building Layzer in public. 15 days, 28 followers. Deciding whether to grab Twitter Premium. Tempted by the reply boost, longer posts, and analytics. What's worked for you? Deciding this week. #SaaS #AI #Startups #IndieHackers #BuildInPublic #Founders #Entrepreneurship

Shipped the first OAuth demo app on Layzer 🔌 User clicks Connect → OAuth handshake (PKCE, refresh, DCR) → tool is live in chat. No API keys, no config files. Demo 👇 #buildinpublic #indiehackers #SaaS #AI

Shipped dev app submission on Layzer 🚀 Any developer can now submit their MCP app to the catalog. Users install in one click — no config files, no API key wrangling. Built an MCP server? Submit at Layzer.ai 👇 #buildinpublic #indiehackers #SaaS #AI

Shipped dev profiles on Layzer 🚀 First step in opening up the MCP apps catalog to external developers. Demo 👇 #buildinpublic #indiehackers #SaaS #AI

Day 14 of building Layzer in public. Twins are doing much better — both just knocked out for the night. A couple of hours of solid Layzer time. Back to the dev submission flow: getting MCP apps into the catalog so users can install them. #buildinpublic #indiehackers #SaaS #AI

@TheSpacerr Probably doable, but you'll need luck and an unfair advantage in your niche. Honestly code was never the hard part. It's the distribution, support, billing edge cases and keeping the thing alive when it breaks at 2am. That's the rocky bit. Vibe coding just speeds up the easy part

Can you vibe-code a real $1M SaaS?

@benfchi @X Hey let's connect

Hey @X Algorithm I'm looking to #connect with builders in: 🤖 AI agents & automation ⚙️ Backend / APIs ☁️ DevOps & cloud 🏗️ Solutions architecture 🚀 Solo & indie founders 💻 Full stack & web dev 📊 SaaS & product growth 🧑‍💻 Vibe coders Say hi and lets grow together! 👋

Day 13 of building Layzer in public. Consistency doesn't mean showing up every day. It means coming back after life happens. Both my boys are unwell, so this weekend is about cuddles, cartoons, and helping them feel better — not code. See you Monday. #buildinpublic #twindad

@harjjotsinghh Next hard part — how do you get devs to build MCP servers for the platform, or adopt their existing ones? Catalog's only as good as the supply.

@harjjotsinghh 💯 config files, manually typing server details — kills adoption for everyone except devs. Let's connect.

@Aran07722526 Done ✅ followed back

@junayed711 Sure wating for your follow!

Heyy devs🤨 How’s your week going so far? Drop your progress • Web Dev • Mobile Apps • AI/ML • Data Science • Open Source • Other cool stuff! Let’s #connect and support each other! :)📷

@ViberankESP Thanks 🙏 will take a look at viberankde

@junayed711 It is inspiring to see your dedication to building Layzer while managing family life and a day job. Consistency is key in the indie hacker journey. You should list Layzer on viberankdev to connect with more developers and get feedback on your progress.

Day 4 of building Layzer in public. Up at 4, gym before twins. They woke early again, Layzer window gone. Day job ate the rest. Zero hours. Winding down with family. Still in. #buildinpublic #indiehackers #SaaS #AI

@devhanzo1 Genuinely good point — I'd been thinking about it as a discovery problem, but you're right that trust is the bigger one. A "what can this actually touch" preview at submit time would be a real unlock. Adding it to the roadmap 🙏

@jndvss Let's connect

So close to 600 followers and I just hit 500 recently, thank you everyone! I‘m always looking to connect with more people If you‘re interested in: 🧰 Building in Public 💻 SaaS 📲 Mobile Apps 🔮 AI 💸 Marketing 💎 UI/UX Design Say hi 👋 and show us what you‘re working on!