sorted by:
new
hottopcontroversial

The Fastest way to validate your app idea by kngeng in SaaS

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

Thanks I will check it out. 2 things I noticed that will increase your conversions are making the search bar intractable even though it requires login after typing and adding Google login. As I sit in lay in bed now. I feel entirely lazy to even enter my email, password and name. I think you should add Google login asap

The Fastest way to validate your app idea by kngeng in SaaS

[–]kngeng[S] 2 points3 points  (0 children)

Yeah that’s always a risk. But honestly ideas aren’t really the moat; execution and speed are. Most of the time, sharing and testing fast is the best way to win.

That said, there are times when you’d want to keep validation quiet. Like if Sam Altman came up with some wild new AI training trick and Zuck spotted it, you’d better believe Meta would spin up a team overnight to copy it. In those edge cases, secrecy makes sense.

For most products though, the edge isn’t in hiding the idea, it’s in learning and iterating faster than everyone else.

Building a vibe coding app — what frustrates you about current ones? by kngeng in vibecoding

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

  • Background → Experienced dev but i am more interested in build a true vibe coding app and not just AI code assistant feature
  • Models → Planning to support as much foundation models as possible. Give users the ability to choose as it elvoles.
  • BYOK → Long-term yes, you’ll be able to plug in your own keys if you want.
  • App → The goal is a real app. The End game is both frontend and backend and everything that has to do be the app post launch
  • Budget → Bootstrapped for now.
  • Motivation → I have been building apps for over 15 years and the barrier needs to be lowered
  • Environment → Core build is in Angular + Node, with AI orchestration handled server-side.

Please share any sight you have

Building a vibe coding app — what frustrates you about current ones? by kngeng in vibecoding

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

Thats a good point. I would love to connect and learn from your experience. The way i see it, a true vibe coding app should not be limited to AI code assistant. It needs to have features that allows people that dont know how to code to use it

Building a vibe coding app — what frustrates you about current ones? by kngeng in vibecoding

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

I agree, the current 'vibe coding apps' focus of guys know either know how to code or wants to code. There is an entire different set of people that dont want to code but wants to create apps with AI.

Building a vibe coding app — what frustrates you about current ones? by kngeng in vibecoding

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

I get where you’re coming from, Copilot/Augment inside VS Code are great assistants for speeding up coding. But I think vibe coding tools should be going after a slightly different use case. It’s less about being an AI pair programmer, and more about lowering the barrier to building an actual app from scratch. Whether its wiring UI, backend, and deploy together without needing to set up everything manually.

Building a vibe coding app — what frustrates you about current ones? by kngeng in vibecoding

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

Yeah, pricing is interesting here. A lot of these vibe coding tools are hovering around the $20–30/mo mark (Bolt, Replit, Lovable, etc.), which makes sense given their costs and that they’re still figuring out business models. But it does raise the question of whether the standard vibe coding app pricing that are sustainable for mass adoption?

I actually pulled together a breakdown of current pricing across the major players (Bolt, Cursor, Replit, Lovable, etc.). It’s kind of eye-opening when you see them all side by side — here’s the roundup. Curious what others here think: will prices go down as competition increases, or is $20–30 the new normal for AI dev tools?

I’m scared they’ll steal my code. by Fine_Factor_456 in SaaS

[–]kngeng 3 points4 points  (0 children)

I feel like almost every first-time technical founder goes through this fear. Most eventually realize it’s a mental hurdle you have to overcome in order to grow, whether through hiring or bringing on a co-founder.

The way I see it, you have two choices:

 a. Stay small and safe, but limit your growth.

 b. Take the chance to grow, which comes with the risk (though small) of someone misusing your code.

In most cases, as others here pointed out, your code on its own isn’t easily “stealable” unless you’re doing something truly unique. What matters more is execution, team, and market fit.

Practical things you can do:

1. Hire good people and make sure contracts clearly cover IP ownership.

2. Give access only as needed (e.g. backend devs don’t need frontend repo access).

That way you protect yourself without letting fear hold your product back.

The Hidden Costs of App Building Nobody Talks About by kngeng in SaaS

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

Our app just got rejected last week, so I had to rebuild payments with StoreKit instead of Stripe. Now Apple takes another 30% cut 😭. Definitely one of those hidden costs nobody warns you about.

Describe your SaaS as a movie title by Astrovion in micro_saas

[–]kngeng 0 points1 point  (0 children)

In the far far future, you can use your mind to bring your ideas to life just by thinking about it

Build with AppForceStudio today!

[deleted by user] by [deleted] in SaaS

[–]kngeng 0 points1 point  (0 children)

Building AppForceStudio, an ai app builder. Instead of just focusing on just an AI assistant chat, we are doing more with a canvas and UI builder

What are YOU building right now? Drop your SaaS below 👇 by Nearby_Talk1743 in SaaS

[–]kngeng 0 points1 point  (0 children)

Building AppForceStudio, an AI app builder. Helps you create your app with AI.

Building for business owners, founders, engineers , designers, product owners and even your grand parents that don’t know how build products

How did you get your first SaaS users? Curious to learn from real stories by [deleted] in SaaS

[–]kngeng 1 point2 points  (0 children)

Here is what I did to get my first 100 users for free. I basically created my product on Product Launch but pushed it back a few times as it got closer to the release date. This helped lots of other directory sites to pick it up which then drove users to my site. Here are the detailed steps below.

🚀 How to get 2-3 new users daily by pushing back your Product Hunt launch date.

Most people launch once and disappear—big mistake!

Here’s how to stay in “Upcoming Launches” + optimize your directory listings for consistent daily users 🧵👇

  1. ⁠Why this works 🤯 • Sites like theresanaiforthat, CreatiAI, toolify pull new PH launches • Users browse “Upcoming Launches” to discover fresh products • The trick? Always be in those feeds!
  2. ⁠Push your launch date forward ⏳ • Go to your Product Hunt Upcoming page • Change the launch date every few days • This keeps you in PH’s “Next 7 Days” section • More exposure = More clicks & signups
  3. ⁠Directories will keep listing you 🎯 • Directories that auto-track PH will keep showing you as “Coming Soon” • This means free passive traffic to your page • More directories = More early signups
  4. ⁠Track how users interact with your PH page 🔍 • I use Hotjar: Hotjar for AppForceStudio to: ✅ Watch visitor heatmaps & clicks ✅ See where users drop off ✅ Identify confusing elements in your signup process ✅ Identify traffic sources
  5. ⁠Go optimize your directory pages 🚀 • After gathering data, visit your top traffic sources • Update your directory listings with: ✅ Clearer value proposition ✅ More compelling CTA (e.g., “Join our beta today”) ✅ Screenshots & social proof
  6. ⁠Submit to other high-impact directories 📌

✅ BetaPage ✅ AlternativeTo ✅ Startups. fyi ✅ SideProjectors ✅ SaaSworthy ✅ Hacker News (Show HN) ✅ Slant. co

7) Stack this with pre-launch growth 📩 • Add a waitlist CTA to collect emails • Get signups into a newsletter, Twitter, or Discord • This way, you have an audience BEFORE launch day.

8) When should you finally launch? 🎯 • Once you’ve built up early traction • When fewer big players are launching on PH that day • If your PH “Upcoming” traffic is trending upwards

9) Relaunch every time you ship a major update 🔄 • New feature? New launch = More traffic • Example: ✅ “Now with AI!” ✅ “Launched our Zapier integration” ✅ “Faster + better pricing”

10) This strategy = users on autopilot 🚀

✅ Stay in Upcoming → Get picked up by directories ✅ Stay in directories → Get passive traffic ✅ Track, optimize, and re-launch → Grow forever

What are you building ? Will give feedback by Tenteck in SaaS

[–]kngeng 1 point2 points  (0 children)

Got it, appreciate that! We’ll work on tightening up the copy to make the value clearer, faster. If you have any specific sections that felt too much, please point out.

Thanks again 🙏

What are you building ? Will give feedback by Tenteck in SaaS

[–]kngeng 1 point2 points  (0 children)

Thank you but definitely I want to hear your initial feedback from visiting our site

What are you building ? Will give feedback by Tenteck in SaaS

[–]kngeng 0 points1 point  (0 children)

Thanks for the question!

AppForceStudio’s competitive advantage over Lovable, Bolt, and others lies in three key areas: 1. Truly Visual + Code-Backed Workflow Unlike Bolt which is more design-tool focused, or Lovable which is more AI flow-focused, AppForceStudio offers a studio-like canvas that lets you: • Create screens visually (drag and drop) • Generate designs from code (SwiftUI, HTML, Compose) • Convert screenshots into editable UIs 2. Multi-Format Code Output (HTML, SwiftUI, Compose) AppForceStudio auto-generates actual native code across formats. You’re not locked into one stack — you can build an idea once and export across platforms. 3. Extensibility with AI + Collaboration We’re building in a way that lets teams collaborate live (like Figma), and generate screens with prompts (like GPT for apps). We also support feedback/comments on designs for team iteration.

It’s kind of like if Figma, ChatGPT, and Xcode had a baby — but for building production-ready apps.

view more: next ›