Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

My career in technology began in Silicon Valley, where I contributed to the development of foundational technologies, including early graphics processing units (GPUs) and the USB 1.0 interface.

Following my time in the semiconductor industry, I transitioned to venture capital, where I focused on identifying and supporting promising technology ventures. This experience fuelled my passion for building and investing in companies that address critical gaps in the market.

Hey Product Hunt community!

I'm absolutely THRILLED to announce that Raven, my slightly sadistic writing app, is officially live on Product Hunt today! This is my first ever Product Hunt launch and I couldn't be more excited to share it with all of you!

Hey Product Hunt community! My first launch today, yikes...

As a publisher and writer, I grew frustrated with writing tools that were either bloated with unnecessary features or completely passive about my constant procrastination. I needed something that would actually hold me accountable.

So, I'm excited to announce that Raven, my slightly sadistic writing app, is officially live on Product Hunt today! It begs the question, what do you find more effective for productivity: Gentle Encouragement or Hard Consequences?

Hi Everyone!
Solving AI audio end-to-end means tackling both generation and understanding - from text-to-speech to speech-to-text and everything in between. At ElevenLabs, we re working on breakthroughs in AI audio that bridge research and real-world use.
Ask me anything about what we re building, the challenges of scaling AI speech models, and where this space is headed. Also keen to hear what you ve built with ElevenLabs! 

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

I ve noticed that the purpose of people on Product Hunt is always different. Of course, the vast majority want to become the Product of the Day, Week, Month, or Year (or win Kitty Awards).

However, some are there for the community and their success metrics may lie in something else (e.g. the number of discussions created and rated).

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

As a PM at Lyft and now building a tool to help PMs and engineers collaborate better with each other and other stakeholders, I ve seen firsthand how difficult alignment, documentation, and decision-making can be. Curious what s been your biggest challenge working across Product and Engineering while building and aligning on documentation, and what has actually worked for you?"

Hello Everyone!

We're building a personalized language-learning app inspired by our own experiences and frustrations with the one-size-fits-all approach of traditional apps. Our goal is to offer customized and adaptive learning paths, powered by user data and tailored to individual interests, goals, and motivations.

I won t go into full pitch mode just yet, but we d love to start a discussion around this question:

• What s your biggest pain point or frustration with current language-learning apps?

Over the years working for agencies I've become quite familiar with tools like @asana and @Jira , also with @Trello for personal projects. But I was wondering, are these the most used or are these just the ones I've been exposed to? Are there better options? Would love to hear your thoughts down below!

In my opinion, the startup scene is not evenly supported, and some countries are not so passionate about business. I'm from Central Europe, and I don't feel any extra entrepreneurial spirit here.
From my observations, countries like France, and Germany (maybe Poland) have always been mainly startup-oriented.

In terms of more favourable taxes for entrepreneurs, Cyprus and Estonia came to mind.

But maybe I'm wrong and I'm overlooking local communities.

Hello Product Hunt friends!

Juan checking in from the community team. Hope your week is off to a great start!

I still can't help but notice that there are not many female tech founders.

However, I ve observed that in some regions, such as India, more women are actively involved in tech.

Similarly, in the Nordic countries of Europe, women seem to have greater exposure to occupations that were traditionally perceived as "masculine."

So, I ve been toying with the idea of going "Build in Public" for my startup, but I m torn. On one hand, it seems like an awesome way to grow an audience, get early feedback, and build trust. On the other, I ve seen plenty of people burn out or struggle to balance actually building vs. constantly sharing updates.

I guess my main questions are:
What s the best way to approach it without it feeling like a second job?
Where do you actually build in public: Twitter, LinkedIn, Reddit, PH, or somewhere else?
Any success (or horror) stories from those who ve done it?

Hey PHunters!

I'm Maria-Cristina. I grew up in a family of creatives and entrepreneurs, always torn between artistic expression and the practical side of business, selling my artwork at local markets when I was barely a teenager.

This is my first product launch, so go easy on me.

I m one of the co-founders of Artefact, but let s be real I m not the one writing the code. My brilliant partners @russell_lowry and @marc__milberg are the true builders. I m the marketing guy, the one making sure people actually hear about this thing and (hopefully) love it.

Hello all, new to product hunt. I am the co-founder of kweeqpay here in Canada. We are building kweeqpay to solve the online scam, and lack of trust problem faced by individuals, small businesses transacting online, especially in low trust environments like buy and sell groups, social media, online marketplaces. I would love to connect with any folks in Canada here that want to give us feedback, intros, etc

Hey all, I've been in startups for 10 years (my last company Outbound was YC-W15, acquired by Zendesk) but my new company splotch.ink is my first on PH! We launched last week and I was very impressed with the community, feedback and results.

I want to invest in this community, so I'm proposing this idea: I'd love to do 20 min interviews with other founders where we talk through key plays/journeys for your business. I'll diagram them out and write them up as a post that we can use as co-marketing to customers and investors. The emphasis will be on key plays that differentiate you from competitors in your UX and ops. Reply if you're interested.

I ve noticed that the purpose of people on Product Hunt is always different. Of course, the vast majority want to become the Product of the Day, Week, Month, or Year (or win Kitty Awards).

However, some are there for the community and their success metrics may lie in something else (e.g. the number of discussions created and rated).