Hey there,
This topic always pops up from time to time.
First, when I started building macOS apps, the extra work of building a trial mechanism was something I wanted to keep for later.
Today, my key management backend already supports that, and when a user personally asks for a trial key, I give it to them.
But from my experience, when someone has a free trial, 2 thing can happen:
1. Download and never use
2. Use a little bit, stop using it, and leave the app without buying it.
When someone pays for the app, they try it most of the time immediately.
He explores the app, finds issues, and, because he paid for it, will be much more involved, which will provide me with much more accurate feedback.
Also, if something is not working well for him, he writes me, and I benefit from these interactions with the users.
A lot of my improvements for my apps are based on "Refund talks"
Overall, the upsides outweigh the downsides.
I don't have many refunds, but when I do, it really helps me improve the app.
I already had users who asked for a refund, and a few versions later, the app improved based on their feedback, and they repurchased it.
I am sure that some users don't buy without trying,
And this is why I am super responsive to refund requests and handle them faster and without "playing games" with this topic.
Maybe,
This has a lot of different opinions,
In SaaS, I can understand why you would give this trial version.
You can improve the onboarding and user progress tracking in the tunnel.
Making rapid updates and improving the onboarding process.
But for Mac apps that nothing is tracked or sent to my server, I have no idea what the user is doing or not doing with the app,
I can't roll out fast updates or even force users to get the newest version
So I won't be able to really improve it.
Maybe in my future Saas I will have some kind of trial.
But for now, I will stay with this model.
Anyway, thank you so much for the feedback,
Super appreciated!
I was speaking from experience selling single-fee end-user Windows apps for about a decade. Trials are basically a must as virtually no one would pre-buy to test.
Perhaps on Macs it's different, or maybe it's due to your price point, but still your approach automatically drives away a large swath of potential, but cautious buyers, or those who don't want to be bothered by the refund process. Your pitch is "here is some good stuff, and here are the hurdles if you want to test it".
I'm not affiliated with them, but I am a customer. They put a lot of effort into finding the right balance of what to unlock upfront in the trial. And their license/unlock process is pretty seamless.
I don't dispute the power of a free trial, but it can be a fair bit of work to get the details right.
Thank you!
Actually, this is not replacing Alfred / Raycast.
I work with Raycase + ExtraBar together.
ExtraBar is really good for managing different tasks in the same app, since there's no direct way to set this up in Raycast/Alfred, and it's also a good place to "bookmark" your favorite Raycast/Alfred actions without having to open the full app.
Raycast provides a deeplink for every action in the app.
So I just take the actions that I use the most and put them in my ExtraBar.
I am working to build full macro creation inside ExtraBar, which will allow you to quickly run complex scripts that use different applications and actions in an easy, accessible way.
Let me know if you have any more question or wants to try it out
Hey,
The price now for the launch month is 9.99 per device.
Prices will be different after it with bundle discounts (but still more than 9.99 per device)
I rounded up by 2 cents for the 2 devices and 3 cents for 3 devices to make the number nicer to read
Users can always buy 2 keys for 1 device separately and receive a 2-cent discount if they like to, I don't limit that option
Thank you!
Glad you liked it
All of my apps are wiht permission free mindset,
So I try my best to find tricks and make everything work without them
For this one, I just removed the need to influence the real apps menu bar items. You build your own menu items, so I handle everything within this app without any permissions.
Good question!
For that I built the floating mode for the app (You can see an example on the website)
You can hide and show it on demand with a simple hot key, of course, so it will be visible only when you need it.
Regarding the similar solution, we don't replace them, instead, we make them much more accessible and integrate with them amazingly well.
A lot of our users are saying that this app is the missing part for Keyboard Maestery and also a huge improvement for Raycast.
Because everything works with Deeplinks, it's super easy to integrate, and with the keyboard-only navigation options, everything is much faster.
Thanks. I think you just need to make this all clearer on the homepage!
The app looks cool but I think the big challenge is in demonstrating what makes it unique/better. You spend time comparing with icon managers, but that is not the competition. It would be much more helpful to me in understanding how it differs from the actual competition. And saying that it is the "missing part" or a "huge improvement" doesn't tell me anything factual.
Don't some of the competitors use keyboard triggers? Do they not also allow you to create deep links? Don't some of them also sit in the menu bar? This is why it's not immediately clear to me what specifically makes your product better. I'm assuming you have an answer, but that's where a feature comparison chart would really help.
Ok, I will try to explain this better
The main power of this app is that I am not trying to compete with them.
I work together with them.
For example, I put my ExtraBar RayCast deeplinks into a logical menu structure so they are easy to access and remember.
Instead of opening Raycast, looking for the actions, sometimes RayCast is opened on a different screen, so I need to go back, etc.
I just put the most used action on the ExtraBar menu and use simple keyboard navigation to trigger it.
The same goes for Keyboard Maestro.
I have this Reddit post that someone posted on ExtraBar:
https://www.reddit.com/r/macapps/comments/1q0aqu6/extrabar_i...
That has some explanation of how he uses it, so this may be helpful to get more usecases example
Ok that's definitely helpful. At this point I'm not really asking questions here for you to answer on HN -- just more pointing out that these are the kinds of things your site needs to explain. What this competes with vs. what it works together with is a great angle.
I assumed ExtraBar was intended to be its own all-in-one solution for executing commands. Now that you say it also works together with other utilities, that changes my perception completely.