[mitch-snipline]

I messaged John on Twitter after he reached out to his followers about Indie apps. Happy to see my app has made the list!

For anyone wondering, it's called Snipline (https://snipline.io). It has very few users, but the people that do use it tend to reach out to me and it's really nice to see the value that they get out of it.

[josephwegner]

Dude, Snipline looks _awesome_. This would be mega useful for me, and pretty much everyone on my team.

The only thing holding me back from committing is the recurring subscription... $9/yr isn't really a lot, but I'm always hesitant to sign up for recurring things because of the likely chance I stop using it but forget the subscription. I much prefer Alfred/Dash style pricing, where I pay approximately once per year for a new "version". Two questions to that point:

1. Are you open to letting people pay once, without setting up a subscription? More of a year-long license model?

2. Do you have any infrastructure setup for teams? I could much easier justify putting this on my AMEX and allowing my entire team access.

[mitch-snipline]

Thanks!

I decided on a subscription to help support the server costs and continue development. I do appreciate that not everyone likes subscriptions and I think that has hindered traction somewhat.

I send out automated emails a week before renewals to remind people about the subscription, and of course I'm happy to refund anyone that mistakenly rolls over.

> 1. Are you open to letting people pay once, without setting up a subscription? More of a year-long license model?

I'd love to do this but both my infrastucture and payment system aren't really set up to do so. I'm more likely to do a limited run one time cost (Pay once and access forever), but I haven't fully decided on that yet.

> 2. Do you have any infrastructure setup for teams? I could much easier justify putting this on my AMEX and allowing my entire team access.

Not currently but I do have some ideas in the works. Either sharing snippets between users, or a public directory where the community can share useful snippets. A team subscription also does sound like a good idea, I'll mull it over :).

For now, since it's all synced to the server, your team could all log in with the same account and share access. Not ideal, but it is a work-around!

[josephwegner]

Yeah, the team sharing stuff (kinda like 1Password vaults) would make this an absolute buy for my team. I manage a technical support team, and we have a _ton_ of CLI commands that we toss around. Part of onboarding is giving people a giant `.bash_aliases` file and a knowledge base article they can read to understand them all. Having that native and searchable would be amazing.

Either way, I've submitted this for a security review (I work at a BigCo, so red tape...). We'll see!

[soneca]

It's very odd for me to conciliate that you work on a big enough company to have red tape and that you are worried about accidental renew of nine dollars per year.

Do you think a one-time license with the price of $1,000 would be an easier sell within your company?

[josephwegner]

Hah. The $9 license fee is something I worry about _personally_.

If I can put this on my AMEX (which is where the red tape comes in), it's a no-brainer. It's an even bigger no-brainer if my team finds it interesting and I can do `$9 * TEAM_SIZE`.

[mitch-snipline]

> Yeah, the team sharing stuff (kinda like 1Password vaults) would make this an absolute buy for my team

I admit it would be useful on my team too, I'll have a think about the best way to implement it.

>Either way, I've submitted this for a security review

I appreciate it, thanks!

[dhosek]

Apple does a good job of alerting you when a subscription is about to renew and you can cancel the subscription but continue using the service before the subscription term ends.

[josephwegner]

But this isn't an iOS app...

[dhosek]

Silly me, I'd assumed it came through the Mac App store.