|
The Steam suggestion is a good one. Unfortunately, the Steam solution has a number of flaws for a product like AB. We've investigated something like it and found it to be no better than what we currently do. All it does it move the issues around, without providing an overall net improvement. In other words, there are some users who would benefit from having a Steam-like solution (such as yourself), but there are others who would be negatively impacted by such a solution.
Even if the Steam approach was the perfect solution, though, we'd need to invest major development effort towards implementing it. For a tiny company like Lone Wolf, we'd have to basically stop further development on all of our products for a protracted period of time while we implemented this mythical perfect solution. From a business standpoint, the benefits of having the perfect licensing solution would have to outweigh the costs of halting all product development for a lengthy period.
In an ideal world, I'd love to conceive and implement the perfect solution. Alas, this isn't an ideal world, so we need something that is also practical, and that means any solution we come up with will have some limitations. If we can come up with something that can be implemented in a practical manner and provides a better overall solution than our current one, we'll put it into place. We regularly explore new options with that goal in mind. Thus far, though, we haven't found something that is substantively better overall.
If anyone has suggestions, please share them! The Steam idea is a good one that we've already explored. What other approaches should we be investigating?
|