Thanks for your reply, I really appreciate it. :) I'll read that article for sure. I have a working app (not mvp yet) and I'm planning to share some screenshots and write about the features in more detail soon.

A working app can be an MVP because it can be shown to potential users...and maybe because minimum viable product is a process?

You have a point, but I think I need at least one week work on it before I can show it without shame. More than half of the functionality is missing and I want to show some of its potential. I'm a bit afraid if I show it with its current state it may scare away users. I don't want people to think it's another useless app (because it won't be, I'm developing it mainly for myself, so I know it's valuable for me). What if I post progress updates and some screenshots or gifs before releasing a beta? What do you think?

I've heard it suggested that when people put up with buggy incomplete software, it suggests that even the buggy incomplete version solves a meaningful problem for those people.

Putting something out in the world is hard because people will probably ignore it and those that don't ignore it will probably say something bad about it because saying something bad is easier than ignoring the bad and seeing the good and because it is easier to say something bad about something another person has built than to build something better (or as good or even worse).

The hard part is often talking to people (also called sales).

Yeah, ignorance is really demotivating. I don't fear criticism even if it's negative, but it's pretty hard to get people to react to something. I'll think about the things you wrote, I'm truly appreciate your replies. Thank you again!