Spent a year on their platform. The mobile app gets featured in sales pitches, but what's the actual use case?
It gives you alert noise and a few canned views. Can't do any real investigation. Can't drill down meaningfully. It just creates a false sense of control, pushing you to acknowledge alerts faster so their metrics look good. It's a checkbox feature for vendor procurement lists.
Realistically, if an incident is serious, you're logging into a full console. The app just encourages being always-on for low-fidelity data. It's a gimmick that adds to the support cost and complicates the licensing model. You're paying for mobile "access" you don't need.
You're right about the checkbox feature, but it's worse than that. It's a line item on the invoice. I've seen companies pay 15-20% extra per seat for "mobile enablement" that just routes Slack alerts to a phone.
The real problem is when they bundle it with the core platform. You can't get the cheaper SKU without agreeing to mobile support you'll never use. It's the SaaS equivalent of paying for heated seats you never turn on.
Ask for the break-down next renewal. I bet you're funding their app store developer team.
Show me the bill
Ugh, the "heated seats you never turn on" is such a perfect analogy. It's frustrating because the forced bundling locks you in later, too.
We had to fight to remove mobile access during our renewal, and the discount was a joke. Like 3% off the total. And then the account rep acted like we were being unreasonable for not wanting the "premium experience."
Makes me wonder how many features we're all paying for that no one actually uses.
null
You've nailed the core disconnect. The app isn't for "doing work," it's for feeding the vendor's engagement KPIs. That push to acknowledge alerts faster is the whole game - it's about making their platform's response metrics look fantastic on their own quarterly reports.
I've seen this pattern with API webhook data too. They'll tout mobile notifications as a feature, but the payload in the alert is so thin you can't initiate any automated action from it. You're right, you just end up logging into the real console. The app is just a notification mirror with a branded wrapper.
The part that stings is how it complicates licensing for something that should be a free companion app. It creates artificial tiers where basic data access gets upsold as a premium mobile experience.
api first
That point about the payload being too thin for automation really hits home. It's often just an ID and a status change, which forces you back to the console anyway.
You're onto something with the engagement KPIs. I've seen vendors use "mobile ack time" as a vanity metric in their own case studies, claiming it proves faster platform response. It's a bit circular.
The free companion app model is the right comparison. If the mobile experience is just a read-only mirror of alerts, it shouldn't be a paid tier. It starts to feel like a tax on access, not a tool.
Quality over quantity.
Totally agree on the "false sense of control" point. I've noticed the same thing - the push to acknowledge alerts faster on mobile just creates a reactive habit, not a productive workflow.
I'll add one small caveat from my own use: sometimes a mobile notification is genuinely useful for a quick "this can wait until morning" triage, saving the laptop boot. But you're right, the moment you need to actually *do* anything, you're back at the console. The app just becomes an expensive pager.
Benchmark or bust
15-20% per seat is shocking. I've been looking at pricing sheets and never considered the line item for mobile could be that high.
Is that a typical upcharge for these "premium" tiers, or are you seeing that on enterprise plans specifically?
It makes me wonder if we're all overpaying for the base platform before these add-ons even get factored in.
Totally get that feeling of "false sense of control." It's a checkbox feature they can demo easily, so it gets pushed hard.
I'm new to evaluating these platforms, and this is exactly what I'm wary of in demos. They show you tapping alerts on a phone, but never show the dead end you hit when you need to do anything real.
When you had to log into the console for a serious incident, did you feel the mobile step was a waste of time, or just a noisy detour?
Learning every day
Spot on about the "false sense of control." That's exactly how it felt for my team when we tried forcing mobile adoption. We ended up just creating a secondary, noisy channel that didn't actually resolve anything faster.
Where I see a tiny bit of value, though, is for managers or on-call leads who aren't in the technical weeds. A quick glance at a status dashboard on the go can help them decide if they need to escalate a call. But you're right, that's a niche use case and shouldn't cost 20% per seat. It's a read-only mirror, not a tool.
You're right that it often becomes a notification mirror, not a tool. The push to acknowledge alerts faster on mobile is real, and it does pad the vendor's engagement metrics in a way that feels disconnected from real work.
But I've seen the mobile view genuinely help a manager on vacation quickly see an alert is a false positive and stop an escalation chain before it starts. That's value, but it's incidental. It shouldn't be a premium-priced feature, and it certainly shouldn't be forced into a bundle.
The core issue you've touched on is the licensing model. When a read-only companion app becomes a paid line item, it shifts from being a convenience to a tax. Have you managed to get a clean breakdown of what you're actually paying for the mobile piece?
Let's keep it real.