3 ms·
In my mind, a trial of the service isn't something that I'd be distributing to end users. If I were trialing your service, it'd be to figure out how it works i
by devmor 3y ago
In my mind, a trial of the service isn't something that I'd be distributing to end users.
If I were trialing your service, it'd be to figure out how it works into my dev process and the decision to purchase would come before I'm sending executable out to anyone but my dev team.
At that point, it's locked in to an extent - I'm not going to want to tell my users "Actually, don't update the app using the automatic updater, go download a new exe instead and use the automatic updater on that one from now on." since that kind of friction can cost a lot of users.
- mike_hearn 3y agoThat sort of trial already works. ToDesktop is a service but Conveyor is a tool, so you provide your own web server in our case. If the web server you set for updates is localhost then you don't have to pay or sign up, you can just download it and use it until you're satisfied it fits. Now, what if you want to distribute within your team? Well, then your compadres would need to run a localhost server too if they want to see updates working. But that's probably OK. This lets you run the purchasing process in parallel with getting it set up if your company is slow to authorize payments (the tool will give you a payment link you can send to anyone).
- devmor 3y agoI think you're in a different bucket than the OP's product, in that case. A fair price to trial at that stage of development is a lot different than charging $99/mo from the get-go. From my view, as a solo dev with a lot of small clients and personal projects, I start a lot of projects that make their way into the hands of collaborators but never make it to a project that's ready to finish. I would loathe to pay that kind of price for those. But if I'm at the point where I have beta testers and other kinds of non-client/dev personnel, I'm a lot more ready to put down significant cash for dev tooling.