Should I spent more time polishing my MVP?

Ship it, and develop incrementally based on user feedback. You don't know(yet), what the people really want it to be. What features they want. May be after 6 months it turns out to be totally different from what you thought.

User's feedback is the solution. Best of luck.

Ship it.
It's never going to be ready/done.

A lot of people saying to ship it, I think are missing a key piece. Something you said makes me want to dig deeper...

I'm scared the design not being neat will scare users away

To me, when I read this I'm hearing "If I ship this and it doesn't get interest, I am worried that I won't be able to tell if it's the idea or the design."

Is this right? If not, feel free to disregard the rest of my message.

In my opinion, if you're releasing a product and not yet sure if the solution you're building is something that solves a core problem for your specific user, you're doing it backwards.

Let me give an example.

I get a lot of flak for this website here because it doesn't sell a product: https://codingcourseproblem.landen.co/

Some people get to the end and think, "so what?" And that's fair.

HOWEVER, I've also gotten tons of feedback from this website. People telling me they really relate to one of more of the pains I've explored on that page. Developers telling me that they felt this way when they were learning, but not now as an experienced developer. Devs signing up as a vote for me to build something to solve this pain.

Now, I have the opportunity to speak deeply to these people, really dig into what the core lacking value of the problem is. Once I know the problem, I can develop a solution.

So, let me ask you... do you know the problem as your potential customers see it? Do you understand how the features your solution has DIRECTLY map to solving the pain your customer has? Have you talked to customers about it yet?

If not, then do that first.

If you have, then hopefully you've built a solution to a real, must-solve problem that users have. If so, then ship it, because your early adopters would rather use an ugly tool that fixes their problem than a great tool that doesn't.

Hope this helps!

Maybe you can ship it now but without marketing it? Then do more and more marketing as the product improves? If you do small marketing things you will get few users but that could be enough to discover crucial feedback, detect some UX issues and bugs. Then, once that's fixed, you will be much more confident in your product and will be able to move to bigger marketing operations, like a product hunt launch.

@hereisnaman @hatkyinc @Kevcon80 @tjeannin @heylorenzut Based on this post I created a way to validate my idea. Would love to learn from your feedback if possible https://www.indiehackers.com/post/artsyspace-a-community-of-people-improving-their-well-being-by-decorating-their-rooms-25106274a6

Ship it if it's working .. no blocker bugs

No.

"Ship it" is probably a good suggestion, but also look whether you can't find an easier way to finish this, seems quite simple and doesn't need a fully custom RoR and Tailwind app. Maybe look for some free bootstrap templates (they look amazing today) and throw them up instead, to start with?

"Launch" today to friends and family, and then begin the iteration while improving the design until you feel more comfortable "launching" it more widely.
Remember the default behaviour is that no one will come to it, you will have to work your arse off to make them, so if they discover your product naturally that's a good thing. Launching isn't a binary event that only happens once https://www.youtube.com/watch?v=3xU050kMbHM&feature=emb_title

Do you have maybe 3 or 4 trusted 'beta testers' that you can ship to initially? They may be able to tell you really quickly whether there is anything wrong, or confusing in the interface. In my experience, this early, limited release is usually beneficial to get some instant feedback of your prototype.

The important thing is to ensure that the flow through your application is logical and not too confusing. From this beta user feedback, make the necessary tweaks, then release to a larger group of early adopters. This way, the second round will have a better initial experience.

I built two products last year, one was built and shipped in a week, and then iterated on. The other was started on September and it's still under development, having undergo multiple redesigns and rewrites. This second product, Sitesauce, could have been launched months ago, but I refused to because "it wasn't ready". I've now realized it won't be ready and plan on launching it soon, so I'd recommend you to save a few months and do it now!

TL;DR: Do it now

I'm in a similar situation a couple of months ago when building https://tenderlist.me. I'm not really a designer, but I'm proficient with CSS frameworks.

I've decided to polish it until I'm happy with it. Besides, first impressions last.

You will know when to draw the line.