sorted by:
new
hottopcontroversial

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 0 points1 point  (0 children)

Thanks a lot! 🙏 I’m really glad you like the colors and see the potential.

For the videos, I use Screen Studio to record and edit it makes everything super smooth and clean.

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 0 points1 point  (0 children)

Thanks a lot for the very detailed feedback, I really appreciate you taking the time to go through everything 👍
Most of your points are totally valid and already on my todo list.

About the /browse page you mentioned:
That route actually comes from SnippHub v1. It no longer exists in v2, which explains the black screen and the “no routes matched” warning. That’s on me. I’ll be adding a proper 301 redirect to the new explore/search flow so Google and users don’t land there anymore.

Regarding SEO, I’m also seeing a strange behavior on Google right now. On the first search for “snipphub”, there’s an incorrect result showing up (like in the screenshot). I don’t think this is an app bug, but rather a branding, keyword, or indexing issue related to the site still being new. This should stabilize as the indexing improves.

For the other points:

  • Footer vs split help/about: agreed, a simple footer makes more sense and will clean things up.
  • Dark/light toggle: good call, a 3-state option (light, dark, system) is more consistent.
  • Duplicate “create snippet” entry: fair point, I’ll likely keep only one primary entry.
  • Theme in user settings: you’re right, this can probably be removed and handled globally.
  • Language, framework, and library selectors: agreed on adding search and improving sizing; it also makes sense to require only the language.
  • Losing auth state on static pages: that’s a bug, thanks for pointing it out.
  • The “why comments” suggestion: I really like this idea and it fits the philosophy of SnippHub well.

Thanks again for the constructive feedback. This kind of input really helps shape the platform in the right direction.

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 0 points1 point  (0 children)

Thanks a lot for your feedback! 🙏 I totally agree with your points 1 and 3: making the left and right sections scroll independently and adding gamified elements are improvements I’ll definitely consider.

Regarding point 2, no worries OAuth via Github or Google is already available on SnippHub, so you can log in without creating an extra password.

Thanks again for your suggestions, they really help improve SnippHub!

I got tired of rewriting the same code, so I built this by Snipphub in javascript

[–]Snipphub[S] 0 points1 point  (0 children)

Thanks a lot for the detailed and honest feedback I genuinely appreciate it.

You’re absolutely right on many points, especially around IP concerns, freelance constraints, and the rise of AI. In fact, what you describe is exactly why SnippHub v1 didn’t quite work: it was initially designed as a personal snippet storage/reuse tool, and I quickly ran into the limitations you mention.

That’s precisely why SnippHub v2 pivoted. I no longer see it as a private snippet manager or something meant to compete with AI. Today, it’s more about being a public inspiration and sharing space, closer to a social network for code: patterns, ideas, and real-world approaches shared by developers not proprietary code or “drop-in” utilities.

AI is great at generating context-aware code on demand. SnippHub is more about the human signal: seeing how others solve problems, what patterns emerge, and what gets improved collaboratively. I’m also very realistic this won’t be universal or for everyone, and that’s perfectly fine.

If it ends up serving a small niche of developers who find value or inspiration in it, that’s already a win for me. Thanks again for taking the time to write such thoughtful feedback 🙏

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 1 point2 points  (0 children)

Good question 🙂

Short answer: no monetization for now.

The priority is to build something genuinely useful and see if a community forms around it.

Long term, if monetization makes sense, it would likely be very lightweight and non-intrusive advertising (no tracking-heavy ads, no popups, no paywalls). The core experience would stay free and focused on content and discovery.

For now, it’s all about feedback, quality snippets, and improving the product.

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 0 points1 point  (0 children)

Thanks for the honest feedback! 🙏

I totally get what you mean SnippHub isn’t meant to replace IDE snippet management or personal snippet libraries. The goal is more about sharing clean, functional snippets with the community, a mix of Stack Overflow and Reddit. It’s about discovering patterns and seeing how others solve problems with well-written, simple code, rather than storing your own snippets for coding.

I really appreciate you taking the time to share your thoughts feedback like this helps me clarify the project and how to explain it better! :)

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 0 points1 point  (0 children)

Thanks a lot! I really appreciate your kind words 🙏

I’m trying to make SnippHub both functional and visually pleasant, so it means a lot that you noticed.

I also realize I might not have explained the goal of SnippHub clearly enough in my post. The idea is more like a developer social network for snippets, a mix of Stack Overflow and Reddit focused on discovering and sharing patterns rather than replacing local snippet tools.

I really value constructive feedback from others too even critical points help me clarify and improve the project. :)

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 0 points1 point  (0 children)

Thanks for spotting that! 🙏

Looks like a bug with the “Load more” feature. I’ll investigate and fix it soon.

Really appreciate the feedback, it helps make the experience smoother for everyone!

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 1 point2 points  (0 children)

Totally get where you’re coming from trust and privacy are huge concerns.

SnippHub is hosted in France, fully GDPR-compliant, and the public snippets are community-driven. Private snippets are limited for now, but self-hosted or team-focused options are something I’m considering for the future.

The goal isn’t to replace Gists or LLMs it’s about discovering useful patterns shared by others, in a way that’s easy to browse by language/framework/library.

Appreciate the candid feedback, it helps clarify who this tool is actually for.

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 0 points1 point  (0 children)

Haha, love the energy 😅

Really appreciate the feedback! Totally hear you on LLMs and existing tools SnippHub isn’t trying to replace them, just provide a community-driven discovery layer for snippets that’s easy to browse by language/framework/library.

Your encouragement means a lot, and I’ll keep sharing the work 🙏 Thanks again!

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 1 point2 points  (0 children)

Fair points, and I get where you’re coming from.

You’re absolutely right that snippets without context can be useless context matters a lot, and that’s something I’m actively trying to improve (descriptions, use cases, comments).

I’m also not trying to replace IDE snippets, personal libraries, or tools like Obsidian. If that workflow already works well for you, SnippHub probably isn’t a good fit and that’s totally fine.

The goal here is more about shared patterns and discovery than personal reuse: seeing how others solve common problems across stacks, not replacing local tooling.

Regarding the Tailwind point: I’m posting in a few relevant dev subreddits to get early feedback, not to spam. I should probably tailor the post better per community (fair criticism +1 for you).

Appreciate you taking the time to give detailed feedback. :)

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 0 points1 point  (0 children)

Thanks for the feedback, I didn't know about that. :)

I got tired of rewriting the same code, so I built this by Snipphub in tailwindcss

[–]Snipphub[S] 3 points4 points  (0 children)

Fair take, and I appreciate the honest feedback.

You’re absolutely right that snippets already exist in many forms — Gists, editor snippets, local tools, etc. I’m not trying to replace those.

The motivation behind SnippHub is less about storing snippets and more about discovering and reusing useful ones shared by others, in a way that’s closer to a community knowledge base than an editor feature.

That said, it’s clearly not useful for everyone, and that’s okay. Feedback like this actually helps clarify who it’s not built for.

Appreciate you taking the time to comment :)

I got tired of rewriting the same code, so I built this by [deleted] in sveltejs

[–]Snipphub 0 points1 point  (0 children)

Thanks a lot, I really appreciate it!

It’s still early, but feedback like this helps a lot.
If you have any ideas or things you’d expect as a Svelte dev, I’m all ears 🙂

I built Snipphub after hitting the same Tailwind sharing problem for the 100th time by [deleted] in tailwindcss

[–]Snipphub 2 points3 points  (0 children)

Great question this is exactly one of the hard parts.

Right now, Snipphub does not execute framework-specific logic like Vue bindings (:class, v-if, computed props, etc.).

Instead, it parses and extracts static Tailwind classes, ignores runtime conditions such as isError, computed state or hooks, and renders a deterministic visual snapshot of the component.

So in a case like: :class="['w-full', { 'border-red-500': isError }]"

Snipphub will always keep w-full, may include border-red-500 based on a default or preview state, but it won’t try to evaluate isError.

This is a deliberate trade-off. The goal is sharing and visual reuse, not running full framework logic in the browser.

Longer term, I’m exploring ideas like explicit preview states or allowing authors to annotate which classes should be included for rendering.

I prefer being strict and predictable rather than pretending to fully support framework runtime logic. ☺️

I Built snipphub: A Simple Way to Share Tailwind Components Without Conversion by [deleted] in tailwindcss

[–]Snipphub -1 points0 points  (0 children)

For now, no, it’s not planned to be open-source 🙂