![]() ![]() Right now my users contact me in these situations and I help them, but again like Colin, I've had increasing numbers of department(/company)-level purchases where this should be something that the customer's IT can manage internally. To be fair, there's a fix for that issue that's being readied for release now, but it's been quite a pain.Īdditionally, there's not a great way for my customers to perform centralized license management, e.g., if a developer leaves and the license should be reassigned to another developer, or if a workstation dies and the same license key should be used on another workstation (this evidently happens more than I'd have thought!). Right now there are some issues with how the solution determines the uniqueness of the underlying machine to which the license is tied such that false negatives are raised from time to time. It works, but it's not without its issues. While I'm generally content with my online payment processor, I'm not entirely thrilled with my license key solution. I've integrated a third-party cross-platform library for license key generation and enforcement that integrates well with my payment processor and operates based on a monthly recurring fee based on the number of active licenses. I also have an online payment processor that operates based on a percentage-of-revenue from each unit sold. Right now I already have code obfuscation via a well-known solution and am happy with that. Like Colin, I've had a few discussions with JetBrains folks around this particular topic and am very interested in what comes of it in the future. I don't think that obfuscation is something JetBrains would have to provide, there are good solutions for that out there already. ![]() If I could just use the standard infrastructure and get a report from the marketplace with stats for all the features starting with cursive.* that would also be great. Stats gathering would be a good example - I have to independently ask permission to do it, write the infrastructure to receive it and the functionality within the editor to send it, and so forth. There's also other functionality that currently I have to duplicate, but which works in annoyingly slightly different ways.If the marketplace allowed bundles of plugins to be purchased, or at least that plugins could participate in the Toolbox that would be good for all concerned, I think. In that case I still have to charge them on top of the Ultimate license and that's problematic. I've discussed this with various users, the issue is that they're used to using P圜harm or RedMine, then eventually they use enough of the functionality and just upgrade to Ultimate and forget about all their license juggling. If JetBrains did take the payment, being able to offer bundles would be really great.It's tricky since it would probably require the user to OAuth or something for permission to use their account, I'm not quite sure what this would look like. If users could take payment using Stripe, PayPal or whatever (I'm using Paddle) and then make an API call to have the licence generated, that would be fine by me. Having JetBrains process payments would be nice too, but is less important than the licence management.If I have to develop a licence server, my customers will have to run two separate licence server processes which do essentially the same thing but work in different ways. Similarly, none of my customers have so far requested a licence server, but I've sold 50 licences each to several customers now so it's only a matter of time. ![]() It is also less complete than JetBrains' solution, for example currently I don't check if multiple users are using the same licence on the same LAN. All this functionality that I have developed was a significant amount of work, requires server infrastructure, may have bugs and works in a different way to how users expect the IntelliJ licensing to work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |