Multi-tool approach works, because everything is best-in-class. Having everything in one tool sounds good, but I'm not sure it would be able to compete with the individual tools.
There's currently two things I miss from these tools:
App performance analysis. There are plenty of tool that provide this, but they tend to be around $99 per month which is a lot of money for something I tend to use occasionally. My use case would be to occasionally analyse and improve performance, rather than track continuously.
Logging. I haven't found a good and affordable tool for this yet. Again, this is something I wouldn't use a lot, until I need to track down a specific issue.
In both these cases added them on-demand isn't great, because it takes some time to get data. But leaving them always running isn't great either as they are quite costly and I don't use them much.
I'd prefer a model where you can always save the data, but only pay when you want to access it.
How do you use Papertrail? I've looked at it, but found the UI kinda confusing. Curious to learn how people use it in practice.
Papertail is easy to be added on Heroku. That's why I've started this. Also, when I have a bug report, I can search it easily in logs. I don't use many monitoring system but for me it's enough still :)
Bugsnag notifies me of exceptions (bugs in my code), and Uptime Robot when my sites are down.
I also configured a few checks with Blazer that notify me when certain SQL queries result zero or non-zero results. For example if there's no new signups for a week, I get emailed.
Nice! Is there anything that the combination of Bugsnag, Uptime Robot, and Blazer doesn't provide you that you wish you had? Would you rather have a single solution, or do you prefer the multi tool approach?
Yeah that's a good point and I'm glad people experiment with different paradigms. Practically speaking though, I usually find the more traditional approach the most intuitive. That's probably partly because I'm used to it, but I believe it's also because it's a paradigm that has stood the test of time and been iterated on many many years.
Great point on the robustess of a paradigm 🔮
I think developers tend to design their app in isolation rather than considering it one of many moving parts of someone using their Mac.
It looking like a classic Mac app is exactly what I want. That way it fees like a native part of the OS and I don't need to learn a new interface. I can rely on my experience of all other Mac apps. Keyboard shortcuts work as expected, window management does too, etc.
When developers get too creative with their interface it usually does more harm than good.
Don’t you think it can limit the arrival of new UI paradigms? Notion or Superhuman are good examples of that, most people love Notion because of the feeling of freedom while using it + the neat interface — it would never have happened with a classic mac app.
I really like the new NetNewsWire: https://ranchero.com/netnewswire/
For me that's a great example of what a Mac app should look and work like.
Marc — The UI looks like a classic mac app, do you have identified what really created this wellness effect while using it?
Will make it more clear!
Let us know how it goes!
Ok, in that case I'd make the landing page all about pricing.
I'd also think about if there aren't any other benefits your approach might have. Maybe having everything happen on my phone is a benefit in that I can mix the automated messages with personal ones.
Or that I can use the same phone number for taking calls, etc.