The license validation has to happen at least every 14 days, there is no interaction by the user needed for this after initial registration and login. Once logged in you just don’t notice it happening in the background. It is also realy only that, license validation. If you use a license on multiple systems you might be prompted to manage licensing if another sytsem already laid claim. Different to the old system (Maxon license server) you can actually do something about blocked licenses now without access to the other system. Different to MSA the number of systems you install Cinema on is not limited, just the concurrent use of the license.
Over all i think that people who are very mobile in where they work now have an easier way to legaly use Cinema on multiple systems, while everyone working on a single system in a fixed location won’t notice any difference after inital login.
It is to early to talk about this in any detail, but we are certainly looking at ways to give users other advantages via the MyMaxon account.
On the development cycle. I can only agree with Kent here. Personaly i hate what came out of the yearly release cycle we had for basically 2 decades now. It forces development in a time based straight jacket that is often hindering things. The development problems we face are so varied that having a one year interval for everything is just not working. It forces Dev, QA, Design, Documentation, Marketing, Sales etc. to intensively focus on and work in lockstep. Being able to release features in a more flexible way will help us to spread the load and work much more efficently. It allows us to spend time as needed, not as forced. In the end we want one thing, to deliver a product that is worth our customers interest and money. The subscription model paves the way to do this. Perpetual release will just be accumulated subscription releases, however many there may be, in a yearly interval. Nothing that costs us much extra effort to provide. The important question for us is not how many customers go for perpetual or subscription, we earn a living with both, but how much more efficient we can work in a less strict timeframe.
If you take a closer look you can see that the reduction to a single version follows a similar logic. Instead of spending time and effort on multiple variations we made things simpler for everyone. Feature development can be a nightmare if you have to try to create a balanced mix for multiple different releases, something we were not able to pull off every time in the past. Fewer releases also mean, a lot, fewer dependency problems.
All in all I realy believe that the switch we made will be to our customers and our own advantage.
Sorry for the rocky start we had, as always things turn out a bit different than planned, but we are working on it.