I chose UNO based on the highly useful modules, whose descriptions I spent all night reading. It all truly looks very promising. I shared the project with partners in three countries, and they expressed hope in the potential to launch projects in multiple countries if I can guarantee what I’ve presented to them.

Waking up one morning to realize that your project, plans, and business have died because one of the crucial project modules is incompatible with a new UNO version or has suddenly stopped receiving updates—that’s not an appealing prospect. Not knowing the license type could also become a critical issue. And this information is not publicly available except for what the dedicated UNO team provides.

Indicating the version of a non-PRO module is good, but for an entrepreneur planning to use a module in their project, it’s essential to know whether this module will be compatible, at least with the next core version of UNO. At the very least, with the next version.

I suggest including this information in the module description, along with the license type (MIT or other) and cost type—one-time or monthly. These are the minimally sufficient details that allow everyone to decide and plan whether to use this module in their project. Seeing the developers' LinkedIn profiles would also inspire much more confidence and encourage purchase and recommendation.

Let’s discuss this. At a minimum, leave a '+' or '-' in the comments if this is important to you or means nothing.

Thank you very much, dear developers. You have truly created and continue to develop an outstanding product. Both the core team and the independent solopreneurs and teams who invest their time and expertise. Creating a great product requires a lot of dedication, and even more so to maintain it.