search

nchudleigh / vimac

Productive macOS keyboard-driven navigation
https://vimacapp.com
GNU General Public License v3.0
3.44k stars 125 forks source link

request: please consider financial sponsorship (via gh sponsors, patreon, crypto, etc) #249

Open phrohdoh opened 4 years ago

phrohdoh commented 4 years ago

vimac is a dream come true! Thank you for the great software.

I would like to give the maintainer(s?) some money to hopefully incentivize further development and as a way to express appreciation. I don't think I'd be incorrect to assume other users likely feel similar.

TL;DR: take my money (as thanks)

phrohdoh commented 3 years ago

https://opencollective.com may be worth considering (e.g. https://opencollective.com/athens)

dexterleng commented 3 years ago

Hi! I think in order for me to justify working on Vimac in the long term (I think there is still A LOT to be done) a sustainable source of income is needed.

IMO Vimac is not the kind of project that would do well with sponsorships, since:

  1. Its a niche product
  2. Its a product targeted towards individuals rather than organizations
  3. I don't have a huge audience

The current monetization model I have in mind is:

  1. Still open-source; Users can build it themselves to run without paying, they get a signed binary by purchasing.
  2. v1 pricing: $30 for 1 machine, $55 for 2, $120 for 5...
    • Discounts for upgrading to v2.
    • I won't implement any paywall or license activation until v1 is complete so I can focus on development

Let me know your thoughts!

ultraGentle commented 3 years ago

I'd be happy to pay according to the model you describe. An alternative would be basic functionality for free but additional features for $.

Separately, in response to

1 - It's a niche product, 3 - I don't have a huge audience

For what it's worth, I think there might actually be a big audience out there that doesn't know it wants this: anyone who has to click a ton every day. An example would be medical professionals who have to enter huge amounts of data, always the same fields, for each patient. This could really speed up workflow, and people are willing to spend for time-saving things.

I think if you keep the implementation simple and intelligible for non-coders, it could be a hit.

Personally, I think the name- and philosophical-connection to Vim won't do you any favors; it may even make many people look away before trying your product and realizing how different it is.