[maury91]

I do agree that job postings asking for personal projects are a little bit over the top.

The main problem with building products is the idea, the spark, honestly I can't see at the moment a product that people need, or even less, a product that I would need

[_mlbt]

I don't worry about what other people need. I build for what I need and if it's not too much effort I also make it available to everyone just in case it's useful to them. A couple examples:

I got tired of configuring emacs by hand for use with Erlang. I had lookup the specific incantation that needed to go into the configuration file every single time. Yes, it only takes a couple minutes and it's not something I do often, but now it's just a simple script away.

https://github.com/dlachausse/erlmacs

Another example: like a lot of people I anxiously wait for certain days to come or need a reminder of just how close we are getting to certain holidays and family birthdays. So I built a quick and dirty app in SwiftUI to countdown the days until a specified date. (It's free with no ads or IAPs, since I built it for my own needs and don't care to monetize it.)

https://apps.apple.com/us/app/countdownula/id6479545149

[llmblockchain]

Ideas are easy. You don't need to think of a new idea (in fact, I highly suggest not doing that). Instead, pick an idea that has been done to death and do it again.

Make a cronjob monitoring service. Make a "privacy focused analytics" platform. Make a session replay service. Make a "javascript error collection" service. Make a user feedback widget as a service.

It doesn't matter what you make. Pick something that has been done before and do it on your own.

If you are hell bent on live streaming-- live streaming that would be far more interesting than watching someone rebuild react.