-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are you willing to pay for RefiAPP? #112
Comments
one-time for a small money is OK. |
Sure if the Refi app already addressed some of critical reported issue for the price ff compare to other Firestore GUI client like Firefoo https://www.firefoo.app/buy maybe $7/month is ok but I'm prefer for one-time purchased |
I would also prefer a one time fee. It would differentiate you from Firefoo which is a subscription. Firefoo is more polished but I don't subscribe there because I don't want another subscription, especially since I only need a GUI sporadically. But a reasonable one-time fee would be good and I would consider it. |
I rely on Refi App on a daily basis for my career as a software developer and for my personal projects. I would pay for either options. |
Thank you so much all broooo. I will try to make an update which fix any critical issue |
Hi, I would be OK with paying one time fee, because touching the firestore DB directly is usually not something you would do on regular basis. I need a tool like this once a quarter. Also if you could setup a donation via GitHub Sponsors that would be great https://github.com/sponsors Cheers |
Hi there, it has been such a long time since Refi app launched and was actively maintained.
Today I had a chance to check out the product and was surprised that many still search for and use Refi APP.
There still some issues in the Refi app but I'm lack of funds to keep this maintained. So I want to make this issue and ask if you are a user of Nimbus, are you willing to pay for Refi App? If yes, which way do you like and how much? It can be one-time, or it can be a subscription,...
The text was updated successfully, but these errors were encountered: