I don’t think that is an intentional business strategy in MOST cases. Usually, it’s an issue of getting a product out the door, then listening to customer feedback on said product and meeting those expectations. I can think of several instances where this backfires on a developer, so I really hope they’re not intentionally releasing half-baked products without expressly announcing it as such.
As a daily reader of these forums, you can sort of use the “Aircraft” threads as a pretty good baseline. Watch the activity on threads really increase as the hype before release. Following release, you can often gauge how successful it was just by seeing how that activity changes. What often happens is a hyped release comes & goes and the aircraft had several bugs & issues, and wasn’t reviewed well. Dev either communicates an upcoming fix or doesn’t communicate at all. Activity on the thread dies as time goes by without a patch. After that, it often doesn’t even matter what the dev does. Once people stop talking about their product, it doesn’t matter that they’ve come back 9 months later & fixed everything. It is imperative that a release is mostly functional ON RELEASE, or people just move on to the next big thing. It’s just very difficult to market new features for an existing product. People just don’t keep up with that stuff. So if it’s not there on release, it’s often written off for good for some customers, as they just don’t often revisit products they’ve already decided not to get.
As for the Aerosoft A330, I find it difficult to get too excited about it without even seeing a feature set.