I understand your point of view, and I agree that too much "perfection" is a bad thing. However, striving for only satisfactory quality could also damage the creator's product. Like all things it's a balancing act :)
Yes. It's all about iteration. Implement a feature functionally but imperfectly, with ideas for improvement on a later second pass; then move on to the next line item while users try the new feature and provide feedback on how to improve it in ways you may not have considered if you'd just spent the extra time to polish it (and may have had to undo some wasted hard work). Then you come back to that feature with user feedback and requests, more experience from working on other aspects of the project, and fresh eyes to review past work under a critical lens.
This appears to be more or less what RalivDev is already doing; not rushing, but not getting overly fixated on the details.