There's a reason you're building what you're building
I've been rebuilding Resgen for a couple months now after pausing for about 6-7 months. At that point, I was discouraged because there were other solutions out there that looked better, had more features, and felt slicker. They had millions of users (supposedly), tons of people saying how much they enjoy using their product (which, of course — it's their homepage), and dozens on staff — how could I possibly compete with that?
But even after using them, there was still this itch that the solutions didn't scratch. Some combination of company messaging, product performance, and output had a mismatch in my brain, resulting in the lingering feeling of "you can build something that looks and feels different, and potentially better, than this".
And so I dove back into my code.
I read a comment on HN a while back that really resonated with me now that I have fresh eyes on Resgen:
Next time you come up with that great idea, don’t Google it for a week. Let your mind fester on the idea, allow it to grow like many branches from a trunk. Jot down all of the tangentially related but equally exciting ideas that inevitably follow. Allow your mind to take the idea far into new places. No, you won’t build 90% of them, but give yourself the time to enjoy exploring the idea totally.
When I do this, once I do Google for existing solutions, I usually find that all the other things I came up with in the ensuing week are far better than what’s already out there. I have more innovative ideas for where it could go next; I have a unique value proposition that the other folks haven’t figured out yet. But had I searched for them first, I never would have come up with those better ideas at all.
All this is to say that the "itch" that you have, and why you're building what you're building, is real. Even if it's just for you. The other products out there just may not land right for you and you should consider that a good sign because, most likely, you're not alone.