Nemanja Pejić, the person who builds NoaLingua

What he is responsible for

Nemanja designs and develops NoaLingua as a single-founder product. That means the person describing how a subtitle line is rebuilt, what a saved card contains or why a permission is requested is also the person maintaining that behaviour in the extension.

The broader project and the reasons behind its local-first design are documented on the about page and in the founder's story.

How articles and comparisons are produced

Product claims are checked against the extension, its source documentation and the live services it depends on. Claims about another product point to that product's own page or store listing and carry a research date. If a behaviour was not verified, the comparison says so instead of turning an assumption into a table cell.

NoaLingua benefits when a comparison recommends NoaLingua. That conflict is unavoidable, so it is disclosed on every comparison and governed by the editorial policy, including the rule that every table must contain a case where the competing product is the better choice.

What counts as evidence here

First-hand product behaviour, external research and one person's learning experience are three different kinds of evidence. The site keeps them separate. Data used by the product is listed with its licence on the data sources page; product limitations are collected on the limits page; and research sources remain linked beside the claim they support.

Corrections and questions

If a claim is outdated or a comparison misses an important distinction, send the exact page and the evidence to the contact address. Factual corrections are treated as maintenance, not as criticism to be argued away.