u/Vast_Hawk_700

built this solo out of bangalore. it's kapyn (https://www.kapyn.app/), ai/tech news as swipeable 30-second cards. inshorts, but only for ai. no paywall, no hype, no 20 open tabs.

the pitch i tell myself: everyone else does ai news loud and firehose-y (x, tldr, every newsletter). i went the opposite way, calm and distilled, one thing at a time. and there's a second half most people never see: "radar", a directory of new ai tools / mcp servers / claude skills. basically "what's actually worth trying this week" instead of just "what happened".

here's the part i actually want roasted:

- ~800 users, all organic, and retention is bad. people try it once, swipe through, and don't come back. i genuinely can't tell if that's an onboarding problem, a "news is a commodity" problem, or a "nobody wants this" problem.

- i keep telling myself the calm angle plus radar is the moat. said out loud it sounds like cope. is "calm ai news" a real wedge or am i just describing a worse version of stuff that already exists for free.

- the landing page and the first 30 seconds in the app, no idea if they land or if i've just been staring at it too long to see it.

so rip it apart. positioning, retention, the name, the landing page, whether radar is the actual product and the news is a distraction, all of it. i'd rather hear the brutal version now than keep polishing something nobody returns to.

what's the first thing that made you go "nope", the concept itself or something in the first ten seconds?

hey, i'm the founder (solo-ish, based in bangalore).

kapyn is an ai/tech news app that works like inshorts, every story distilled into a 30-second swipeable card. calm, no hype, no 20-tab doomscroll. there's also a section called radar: a curated directory of new ai tools, mcp servers and claude skills, basically "what's actually worth trying this week" instead of just "what happened".

it's a pwa, so it runs in the browser and installs to your home screen. no signup, no paywall, nothing to type in before you can use it. link: https://www.kapyn.app

what i'd genuinely love feedback on:

- onboarding: does the first card make sense in about 5 seconds, or are you confused about what this even is

- the swipe feel on mobile, is it smooth or does it fight you

- the radar: would you actually try anything from it, or does it read like every other tool list

- the honest one: ~800 people have tried it and most don't come back. i want to know what would make you open it again tomorrow, what's missing on day 2

no premium tier to dangle since it's free forever, but i'll happily test your thing back and leave real notes, drop a link in a reply and i'll dig in.

what's the first thing that made you want to close the tab? that's the answer i need most.

been cataloguing MCP servers for a bit and the same 5 get recommended everywhere (github, filesystem, postgres...). the more useful ones are further down the list. the underrated ones imo:

- Context7 - pulls up-to-date library docs into the model, kills the

"trained on 2023 docs" problem

- Stagehand - automate a browser with plain-english instructions

- Vibium - basically "selenium for AI", self-healing browser tests

- Cypress - run + inspect your e2e suite from the assistant

- Zep - long-term memory with semantic search across sessions

- E2B - run model-generated code in an isolated cloud sandbox

- Sentry - pulls real error/perf context into the chat

- Desktop Commander - run terminal cmds + edit local files

what am i missing? genuinely trying to find the ones that aren't on every listicle. full directory is linked below (i maintain it, it's free, no signup).

Most people know BRSR exists. Fewer realise what actually filing one takes.

The short version:

• It's mandatory for the top 1000 listed companies by market cap (SEBI).
• Section C alone is 108 disclosure fields across nine principles: emissions, energy, water, waste, workforce, human rights, community and consumers.
• BRSR Core attributes (GHG intensity, energy, water, waste intensity) now carry a reasonable assurance requirement on a phased glide path. That changes things: an auditor asks for the evidence trail and the named data owner behind every number, not just the number itself.
• Value-chain disclosure is coming (FY 2026-27), pulling in significant partners including unlisted suppliers. If you supply a listed company, this can reach you even if BRSR doesn't apply to you directly.

The part that surprises most finance teams: a lot of the data already exists inside the company. Pollution Control Board consents, EPR registrations, PAT returns and hazardous-waste manifests already cover a meaningful chunk of the environmental disclosures. The real work is knowing which ones, and then chasing the rest from five different teams who've never heard of BRSR.

That's why the first week of a BRSR engagement is mostly archaeology rather than analysis.

Happy to answer BRSR questions in the comments.

Bangalore-based, building solo(ish). Sharing partly to give back and mostly because I'm stuck on the hard part.

What I built: Kapyn (https://www.kapyn.app/) , AI/tech news distilled into 30-second swipeable cards (think Inshorts, but only for AI). No paywall, no hype, no 20-tab doomscroll. It also has a "Radar" for new AI tools, MCP servers, and skills.

Where I am: ~800 users, mostly organic + friends. People consistently say "nice concept" but a lot open it once and don't come back. So I have an acquisition trickle and a retention hole, and I'd rather hear the hard truth than another "looks clean."

What I'd genuinely value your take on:

1. When you open something like this, what would make you come back tomorrow? (I suspect passive news isn't a daily habit on its own.)
2. Is "AI news, but calm" a real need for you, or a nice-to-have?
3. What do you use *instead* to stay current on AI?

Full disclosure: I'm the founder.

I've spent the last few months building Kapyn, a calm, curated map of the AI worth using (tools, models, MCP servers, skills) + a 30-second daily brief. Solo, free, no paywall. Sharing the honest build, not a pitch.

How it's built:

1. Next.js PWA, Supabase for data, Gemini to auto-summarize AI news on a daily cron, with a quality filter that drops hype, prompt leaks, and low-signal changelog noise (the summarizer was the hardest part to get calm instead of clickbait).
2. A deliberate product call: curated, not comprehensive, ~119 tools, not a 12,000-link directory where half are dead.
3. Just shipped a desktop-vs-mobile front door (computers get a real landing page, phones get the app) because cold visitors were landing on a tiny phone mockup and bouncing.

The honest result: ~2–20 daily users. ~10–15 people tried it, said they "like the concept," and never came back.

What I got wrong (the real learning): I over-built polish and under-built the reason to return.

"I like the concept" isn't retention, it's politeness. AI news is a commodity (Artifact died on exactly this). The fixable miss: no return trigger, push was built but switched off, no email, and the feed only refreshed once a day, so a second visit looked identical to the first.

What I'm doing next: turning on a real trigger (web push + daily email + refreshing content every few hours), talking to the people who churned, and narrowing to one audience instead of "everyone into AI."

If you've built a content/discovery product, how did you crack the return habit? That's my wall. Link if you want to poke holes: kapyn.app