38 karma · joined March 8, 2016
The credit card being in Microsoft's hands is just another surface that my card is exposed to, perhaps I'm being over zealous worrying on that front.
It means I have to sign in to windows: I have to deal with it nagging me to change my standard logon to a microsoft logon. I then have to worry about all the other apps and their permissions, privacy implications now and in the future.
I have to give my credit card details to microsoft. I can't easily take the software with me if I need to use another machine/laptop/tablet etc without having to, again, sign into windows in some way and have all of the above congnitave overhead *n machines. Hell even if I make another local user account for testing or whatever I can't even use your software as I again have to sign into windows even though its working for my main logon.
It all adds up to another thing that needs managing/thinking about, which pretty much takes the convienience of (your software, in this case) away.
If you wanted to make it restrictive and painful for your users, you have succeeded!
However the template system is in XAML which is fine if you're au fait with that but can be a bit fiddly to get what you want.
The only other issue I have with it is that the full version - which is definately worth the money - is distributed via the windows store which forces you to have an account with Microsoft. Overall though, excellent.