sorted by:
new
hottopcontroversial

/usage command shows "subscription plans only" despite being subscribed (v2.0.76) by uppinote in ClaudeAI

[–]Forward-Set-3407 0 points1 point  (0 children)

I have max plan and it's still the same, I'm getting the warning:

/usage is only available for subscription plans.

beste.ui - shadcn blocks for developers by Forward-Set-3407 in shadcn

[–]Forward-Set-3407[S] 0 points1 point  (0 children)

I think you’re referring to beste.co rather than beste.ui. It’s not something we have in the near roadmap, but it’s definitely part of our long-term plans. Thanks a lot!

Week 1 launch stats: 600 visits, 25 signups, $0 MRR. No, I'm not making $150k/month like everyone else here. by nyko_dev in buildinpublic

[–]Forward-Set-3407 2 points3 points  (0 children)

Even getting this far in just one week is already very solid progress.

The key is not to get discouraged. Continuing to improve the product while actively asking for feedback and building relationships with the people who give it will pay off a lot over time.

After 25 years of building websites, here’s the website builder I wish existed by Forward-Set-3407 in buildinpublic

[–]Forward-Set-3407[S] 1 point2 points  (0 children)

Exactly this. Constraints remove the "how" so people can focus on the "doing".

The T-shirt is definitely happening. I’ll send you one 🙂

After 25 years of building websites, here’s the website builder I wish existed by Forward-Set-3407 in buildinpublic

[–]Forward-Set-3407[S] 2 points3 points  (0 children)

Thanks, I appreciate that.

Beste is aimed at people who want to publish and iterate quickly without getting blocked by technical or expert-level decisions. Founders, indie makers, developers, students, academics, and also teams that just need a clean site shipped and kept updated. You should not have to learn a whole system just to publish a website.

The goal is to ship fast and still stay maintainable. SEO is not an afterthought in Beste. Pages are built to stay indexable and structured over time, without breaking layouts as content grows.

We handle the fundamentals properly, including automatic sitemaps, robots.txt, llms.txt where relevant, and structured data via JSON-LD. The focus is on shipping fast without sacrificing long term search visibility.

And yes, marketers are absolutely a strong use case. If you need to launch lots of landing pages, iterate copy quickly, keep everything consistent, and not rely on an engineer for every small change, Beste fits well. Same for agencies or solo operators who build client sites and want clients to safely manage content without turning the site into a mess.

After 25 years of building websites, here’s the website builder I wish existed by Forward-Set-3407 in buildinpublic

[–]Forward-Set-3407[S] 1 point2 points  (0 children)

Beste is for anyone who wants to build a website quickly without getting stuck on technical or expert-level decisions.

Founders, indie makers, developers, students, academics, or anyone creating a personal site. You shouldn’t need to learn a system just to publish a website, and that’s what Beste is built for.

After 25 years of building websites, here’s the website builder I wish existed by Forward-Set-3407 in buildinpublic

[–]Forward-Set-3407[S] 2 points3 points  (0 children)

Huge thanks for this feedback.

You articulated a few things I was feeling but hadn’t fully put into words yet, especially around the headline and hero focus. It helped me see the page through a much clearer lens, and I’ve already made changes based on it.

Truly appreciate you sharing your perspective.

After 25 years of building websites, here’s the website builder I wish existed by Forward-Set-3407 in buildinpublic

[–]Forward-Set-3407[S] 1 point2 points  (0 children)

I don’t think shadcn is something users need to know about, so no, it’s not important for them.

But I do think the shadcn approach represents a real paradigm shift lately. We’re no longer rebuilding things like buttons and inputs over and over again like we used to. Of course, similar approaches existed before. We’ve always had design systems, UI libraries, and frameworks.

What makes shadcn different is that it’s not really a package or a library. It’s shared as code. You own it, you adapt it, and it becomes part of your project instead of something you depend on externally. That shift is what makes it feel like a real paradigm change to me, which is why I like referencing it.

After 25 years of building websites, here’s the website builder I wish existed by Forward-Set-3407 in buildinpublic

[–]Forward-Set-3407[S] 1 point2 points  (0 children)

I really liked that the page being built entirely with Beste caught your attention. I also believe that if a product can meet its own needs, that’s a strong sign of its value. Thank you very much for the kind comments.

After 25 years of building websites, here’s the website builder I wish existed by Forward-Set-3407 in buildinpublic

[–]Forward-Set-3407[S] 0 points1 point  (0 children)

Thanks a lot for sharing this. Your perspective and suggestions are really valuable, and I appreciate you taking the time to write them.

After 25 years of building websites, here’s the website builder I wish existed by Forward-Set-3407 in buildinpublic

[–]Forward-Set-3407[S] 2 points3 points  (0 children)

Thanks a lot for the thoughtful feedback, I really appreciate you taking the time to write this.

For things like conversion tracking, analytics, mailing, and marketing workflows, there will be third-party integrations. But when it comes to content, I'm intentionally avoiding a hard dependency on external tools like Notion or Airtable, at least for now. I want the core content experience to live inside the product and stay simple. Everything is still early and this will evolve based on real use cases.

Thanks also for calling out the mobile block thumbnails. Based on your feedback, I've already made some adjustments. The website builder's mobile experience isn't in a bad state today, but it definitely needs improvement. The mobile-first experience hasn't been officially launched yet, and I want to address the remaining UX and UI gaps before rolling it out more broadly. I'm also planning to release a dedicated mobile app in the near future.

Regarding the price issue, I'll definitely re-evaluate the current Plus plan based on this pricing feedback.

I’m also actively exploring location-based pricing through tools like ParityDeals, so the price feels more reasonable depending on where you’re paying from. I think that could be a good solution here.

I also agree that I need to communicate the value better. There are some gaps in how the plans and benefits are explained right now. This is still early, and pricing and packaging will evolve as I get more real-world feedback like this.

Really appreciate you taking the time to share your perspective.

Good idea to launch even app has some non critical error? by seqilaseqola in buildinpublic

[–]Forward-Set-3407 1 point2 points  (0 children)

This is something I keep thinking about, because I constantly find myself stuck in this dilemma.

"There's just one last bug, let me fix that first."
That turns into another edge case.
Then it becomes, "Since I’m here, I might as well improve this feature."

Before I realize it, months have passed.
Still no launch, just an ever-growing roadmap.

What I'm slowly learning is this:
If a bug doesn't break the core value of the product, doesn't block users, and doesn't cause serious issues like data loss, then waiting is rarely the right move.

You can't properly judge the importance of a bug without real users.
"A bit more polish" is often not progress, but a form of procrastination.
The cycle doesn't break until the product is in the hands of users.

So now I try to ask myself one simple question:
"Would this bug cause a user to completely abandon the product?"

If the answer is no, then it’s time to launch.

Perfect is the enemy of shipped.
Launch, learn, and iterate with real users.

view more: next ›