We've spent almost two years building an e-commerce platform, and we're now facing a decision that I think many founders eventually run into.

Do we keep it closed-source and build a hosted SaaS business around it, or open-source the platform and try to build a community around it?

Last night I was still working at 1AM. Everything I actually meant to ship was done by six. Then I kept going and generated a few sets of slides for my next PH launch. 

Two years ago, I would have ended by eight. Not because I had more discipline - because I would have needed a designer, needed to wait on my devs. The day ended when I ran out of things I was capable of doing alone. 

When mass layoffs started in tech, many people suggested that:

1. The layoffs were happening because, during COVID, companies hired too many people for online and remote roles.

2. That AI was attacking jobs.

And I still keep seeing statements from creators of various AI tools saying:
No, AI won t replace you. Employees will just have time for more meaningful tasks in a company.

We were picking a CRM for the studio, and I went down a hole. Ended up reading about 180 reviews of the best-funded tool in the category. $116M raised, most of it this year. G2, Capterra, Trustpilot, the app stores, a pile of Reddit threads.

I expected the complaints to be about missing features. Nope.

Hey everybody,

Yigit here! I am developing a personal finance app mainly based on what features I wish an app to have and it is on google play closed test now. Here is a quick summary:
The app's main value proposition is being able to keep track of your expenses 'automatically'. The rationale behind is the fact that in my country banking laws restrict individual's access to open banking apis. That is, you cannot have an API access to your bank to exchange information and keep track of your expenses unless you are corporate. According to my research, this feature is available in US and EU but only with certain restrictions in the latter.

I thought it could be sutaible time to ask the community about their needs about such an app and can guide me a long way before I commit further. Would you be so kind enough to answer below questions? Any replies are appreciated and thanks in advance.

1. Do you use personal finance app?

2. Could you please share your the most essential must-have features of the personal finance app of your choise and tell me why?

3. Under which circumstances would you give another app a try?

4. What would be the ideal price point for such a service in your perspective?

I m testing my iOS app on an iPhone running a pre-release/beta version of iOS.

When trying to leave an App Store rating/review, I get this message:
You can t write reviews while using a prerelease version of iOS.

Has anyone faced this issue before?

Is there any official way to submit an App Store review while staying on the iOS beta, or is using a device running the public/stable iOS version the only option?

Personally, I was laid off a year ago and currently bottoming out on savings. Every day is not guaranteed, quite literally, at this point. Yet, I keep my head down and continue building out a product relentlessly that I, quite frankly, have no idea how it will turn out.
Many of us took this leap of faith and are under strenuous circumstances, especially in the current market. If you're in similar positions, just know that everything will work out! Fortune favors the bold.
We're in this together! I would love to hear your stories.

Finding interesting software is easy, but keeping track of it is a mess. Every week I come across several tools on Product Hunt, think "that looks useful," close the tab, and forget the name within an hour. Then, when the exact problem pops up weeks later, I cannot remember what the app was called.

Right now, my system is just a single notes document crammed with dead links and half-finished descriptions. It does not work.

How do you keep a shortlist of software you want to test? Do you use browser bookmarks, a dedicated notes app, a spreadsheet, or a read-later queue? Also, do you actually check back through your list, or does it turn into an unorganized graveyard?

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.