Sorry, you lost me here on your game analogy. I haven't played games for a while. Or maybe our understanding of DRM term differs. I have never heard before use this term in the context of a software, more with books and music.
How does my solution differ from something that Postico and Sublime Text are doing?
My plan is to offer a fully featured application for free, but with slightly annoying pop-up that users can remove by paying a (reasonable) one-time fee. Is there a better way to go about this? I'm really curious.
So the only thing the whole licensing framework will do is get rid of the nag? That wasn't my understanding of your post at all. I thought the program wouldn't work at all if it weren't properly licensed.
Not all licensing features have been rolled out yet, so let me briefly explain the overall vision.
DevTUI will be available to everyone as a free product, with no limitations on functionality. However, it will include a nagging popup prompting users to support further development. Users can remove this nag screen by paying a (reasonable) one-time fee.
The inspiration for this payment model comes from Postico and Sublime Text — two products I personally support and admire.
Since DevTUI doesn’t incur any recurring costs, I’m okay with people using it for free. That said, I still want to encourage users to contribute financially to the project rather than relying on the usual “begging for open source funding” approach.
How does my solution differ from something that Postico and Sublime Text are doing?
My plan is to offer a fully featured application for free, but with slightly annoying pop-up that users can remove by paying a (reasonable) one-time fee. Is there a better way to go about this? I'm really curious.