Arif Hossain

I understand the frustration about pricing, and it’s completely fair to decide that a product isn’t worth the asking price for your use case. However, I think this review mixes legitimate criticism with a number of assumptions that aren’t directly related to the product itself.

The price of a premium plugin is ultimately a business decision. Nobody is forced to buy it, and whether it’s worth $800 depends entirely on the customer and the value they expect to receive. For agencies or businesses deploying it across many projects, the calculation may be very different from that of an individual user.

Criticizing the roadmap is fair if specific promises have been missed. But saying the company has “too many products” without pointing to concrete examples doesn’t really help other potential customers understand the actual strengths or weaknesses of FluentPlayer.

The comments about where the company is registered, labor costs, or calling it a shell company also don’t say anything about the quality, performance, security, or support of the plugin. If there are technical issues, missing features, bugs, or licensing concerns, those would be much more valuable for prospective buyers.

Constructive criticism backed by real-world experience helps everyone. General frustration is understandable, but separating business opinions from technical product feedback makes reviews far more useful.