[ojame]

I've learn't a lot about this for my product[0]. Often teams deploy web apps multiple times a week (or day!) so having a time based trial works. For web extensions, some teams release once a week, others once a month and some a few times a year. When you're at the mercy of a review cycle (Chrome Web Store can take hours to days), it really impacts how rapidly you can release your work.

If I had a 2 week trial - those that submit web extensions to stores rarely wouldn't see the benefit of the product before their trial was over. I made it simple and capped it at 5 successful submissions. Success is important here because you can go through the review cycle 5 times ('5 failed submissions' - this number could change, but it works for now) and then your trial would be over. At the end of the day, regardless of how fast teams work, I want everyone to see the value under the same conditions.

I've worked at places that are focused on time trials because there's no practical way to limit the product in another sense that would give users time to fit in their workflow but also limit their actions enough to convert. Perhaps that's a failure of the scope of the product etc. but it works well enough for them.

0 - https://atriumapp.dev

[wahnfrieden]

Did you test conversion or is it your untested hypothesis that threat of cutting off a trial before so many valuable interactions converts worse than waiting on further use. You have a logic but unclear if it matches reality

[danpalmer]

I love it. Great product, looks like a good price, and I like the 5 successful submission trial, it makes complete sense.

[jimkleiber]

Just a heads up: typo on your site of "Sumbission times"