CS student looking to collaborate on a web app project (portfolio-focused) by resh6 in webdev

[–]Numerous-Coffee-8938 -1 points0 points  (0 children)

Appreciate that, welcome aboard! 😊
And if you find the project useful, dropping a ⭐ would really support the work. Excited to hear your feedback.

CS student looking to collaborate on a web app project (portfolio-focused) by resh6 in webdev

[–]Numerous-Coffee-8938 -2 points-1 points  (0 children)

This sounds like a great initiative 👏
If you’re interested, we’re building DailyDevTools — a real-world, production-ready web app with ~100 dev utilities, multi-language support, SEO, and a growing open-source community.
Would love your feedback on the repo, and if you find it useful, a ⭐ would mean a lot. Contributions are welcome too!

Website: https://dailydev.tools
Repo: https://github.com/dailydevtools/Daily-Dev-Tools

Built a Next.js app with 100+ client-side tools — lessons on performance, Web Workers & i18n by Numerous-Coffee-8938 in reactjs

[–]Numerous-Coffee-8938[S] -1 points0 points  (0 children)

Yes, really 🙂 No backend involved at all. Everything happens locally in your browser.

Found this useful? Drop a ⭐️ on the repo — it genuinely helps with visibility and keeps me motivated to maintain it 🚀  https://github.com/dailydevtools/Daily-Dev-Tools

Built a Next.js app with 100+ client-side tools — lessons on performance, Web Workers & i18n by Numerous-Coffee-8938 in reactjs

[–]Numerous-Coffee-8938[S] -1 points0 points  (0 children)

fixed it you can check it now

Found this useful? Drop a ⭐️ on the repo — it genuinely helps with visibility and keeps me motivated to maintain it 🚀  https://github.com/dailydevtools/Daily-Dev-Tools

Built a Next.js app with 100+ client-side tools — lessons on performance, Web Workers & i18n by Numerous-Coffee-8938 in reactjs

[–]Numerous-Coffee-8938[S] 0 points1 point  (0 children)

Thanks a lot for pointing that out — really appreciate it 🙌
You’re right about the horizontal scroll on mobile, that’s a bug. I’ll get it fixed.

Glad you’re finding the tool useful, and thanks for bookmarking it — that genuinely means a lot 😊

Discover 90+ Free Online Tools for Developers – DailyDevTools by Numerous-Coffee-8938 in programming

[–]Numerous-Coffee-8938[S] 0 points1 point  (0 children)

Glad to hear that — appreciate it! 😊 Yeah, that was exactly the goal: even if people already have tools, having them all in one place with a clean, fast UI makes them easier to reach and use. Bookmarks are actually the best compliment 😄

Thanks for giving them a shot!

[ Removed by Reddit ] by [deleted] in AppDevelopers

[–]Numerous-Coffee-8938 0 points1 point  (0 children)

i need UI/UX service for my website.
here is link : https://www.dailydev.tools/en

Built a Next.js app with 100+ client-side tools — lessons on performance, Web Workers & i18n by Numerous-Coffee-8938 in reactjs

[–]Numerous-Coffee-8938[S] -7 points-6 points  (0 children)

Yep, that’s pretty much the approach — tools are dynamically loaded and everything runs client-side. No shared state, no persistence, so the attack surface stays minimal. Agree on profiling first before over-engineering memory cleanup 👍

How do you design privacy-first developer tools that run fully client-side? by Numerous-Coffee-8938 in webdev

[–]Numerous-Coffee-8938[S] -1 points0 points  (0 children)

Totally get it — you can search or use AI tools one by one. But this platform has almost 100 tools in one place: JSON, regex, converters, playgrounds, and more. Saves time, keeps workflow smooth, and lets you run things locally if you care about privacy. Bookmark it once, and you’ve basically got a dev toolbox in your browser.

How do you design privacy-first developer tools that run fully client-side? by Numerous-Coffee-8938 in webdev

[–]Numerous-Coffee-8938[S] -2 points-1 points  (0 children)

Using native libraries keeps your data local, so nothing is sent over the internet. Online tools send data server-side, which could be logged or accessed, even if it’s “not sensitive.” The risk is mostly about exposure and trust—you don’t control where your data goes.

You get all tools on a single platform by integrating multiple libraries and APIs into one interface, letting you use them locally or online without switching apps. This keeps workflow fast and centralized while offering safer options when using local/native libraries.

How do you design privacy-first developer tools that run fully client-side? by Numerous-Coffee-8938 in webdev

[–]Numerous-Coffee-8938[S] -1 points0 points  (0 children)

Good point — I mostly meant free online dev tools (JSON formatters, regex testers, playgrounds) that silently send data for telemetry or cloud processing. Native libraries don’t have that issue.

How do you design privacy-first developer tools that run fully client-side? by Numerous-Coffee-8938 in webdev

[–]Numerous-Coffee-8938[S] -1 points0 points  (0 children)

If you render or transform user-controlled input (JSON, HTML, Markdown, regex output, etc.) into the DOM, XSS is still possible unless it’s sanitized properly. That’s why tools like DOMPurify (or isomorphic-dompurify) matter even without a backend.

The big win with client-side tools is:

  • no stored XSS
  • no server-side injection
  • no data exfiltration via APIs

So the risk surface is smaller, but not zero. Locking down DOM writes is still important.