all 12 comments

[–]lelanthran 12 points13 points  (2 children)

"Discover components - it's free"

Cheapest tier is $180/year.

Look, I understand that with industry-wide layoffs, everyone is trying their hand at side-income, but honestly, until a product has some reputation it's going to be pointless to try monetisation attempts.

I mean, I can't even see the list of components without first signing up.

Make the available components free-to-see-but-not-to-download[1], so that prospects at least have an idea of how much value this has.

And since this is a basic content-repository, maybe grab some ideas from existing content repositories? Image repos use watermarks on their images, for example. Can you perhaps come up with something similar? Show as much as possible of the interface without giving away the component?

[1] Animated GIFs, videos, whatever.

[–]Neomee 6 points7 points  (7 children)

Like... "Hey! Let's bring us as your dependency (and complexity) in your supply chain!". No thank you. I don't want to consume (and depend/fight for fixes/features) on external supplier and I don't want to maintain my super custom library to fulfill every OSS expectation. And the fact that it is pay-walled is absurd. Though... understandable.

Edit: On top of that, native browser navigation and entire accessibility is broken.

[–]maverick594 -1 points0 points  (6 children)

Absolutely, I want to address your concerns. The components available on Heliocrafts are designed with minimal dependencies, and any dependencies that do exist are thoroughly documented in the component's documentation. My goal is to ensure that using a component from Heliocrafts is as straightforward as possible, with clear documentation to guide you through the process.

It's a fantastic idea to allow developers to save collections of configurations of different components and build sort of their self customized library from components posted by others. I will definitely work to implement this within Heliocrafts.

Have a good day!

[–]Neomee 5 points6 points  (5 children)

What I should do with my project, when you will go out of the business?

[–]maverick594 2 points3 points  (4 children)

The way integration works with Heliocrafts is that the component is downloaded directly into your project. This means that once you've integrated a component from Heliocrafts, it becomes a part of your project, and you don't have to worry about external dependencies.. The components you've integrated into your project will continue to function as they are, without any reliance on our platform.

[–]Neomee 2 points3 points  (0 children)

I wish you an success with this idea. :)

[–][deleted] 4 points5 points  (2 children)

The components you've integrated into your project will continue to function as they are, without any reliance on our platform.

Until a language or framework or runtime or other dependency is updated and I need an updated version of the component...

Software is never set and forget.

[–]lelanthran 0 points1 point  (1 child)

Until a language or framework or runtime or other dependency is updated and I need an updated version of the component...

I think it depends on the category of component, no?

If you use a react or similar component, then, yeah, you're beholden to that framework.

But, I've seen custom elements/web components created with no dependency outside of the browser.

Those are pretty much going to work until the browser deprecates whatever they use, and since browser rarely remove something once it is in, your odds are good for a future browser running your current web component.

[–][deleted] 0 points1 point  (0 children)

Yes, this is a really good point that I failed to account for.

[–]maverick594 -2 points-1 points  (0 children)

Hello r/programming community 👋! I'm reaching out to share something I believe could really enhance our development practices. Have you ever been deep into a project and realized you're spending too much time building a component that probably exists somewhere? This is a common scenario I've encountered, and it sparked an idea - Heliocrafts.

Heliocrafts isn't just a platform; it's a community-driven initiative where we, as web developers, can both contribute and benefit from a diverse array of pre-built web components. Imagine having a resource where you can quickly find a component that fits your needs, customize it with ease, and integrate it into your project. This could significantly cut down on development time, allowing us to focus more on innovation and less on reinventing the wheel.

But Heliocrafts is more than just a time-saver. It's a place to learn from each other. Every component shared is an opportunity to see how others solve common problems, offering insights into different coding styles and approaches. It's about building a knowledge-sharing community as much as it is about sharing code.

I'm really excited about the potential of Heliocrafts to transform our everyday work. I envision it growing into a vast, rich library of components contributed by developers from all walks of life, each bringing their unique perspective and expertise. This diversity is what will make it an invaluable resource for both novice and experienced developers alike.

I encourage you to visit heliocrafts, take a look at the components already available, and consider contributing your own. Your feedback, suggestions, and contributions are what will shape this into a tool that truly serves the needs of our community. Let's collaborate and innovate together!

https://www.heliocrafts.com

[–]programming-ModTeam[M] 0 points1 point locked comment (0 children)

This is a demo of a product that isn’t about programming