Okay, I love Opus Clip's web platform for creating quick clips, but the mobile app? It feels like a completely different (and broken) product.
I tried to clip a video from my phone's library yesterday—constant crashes. When it did load, the export failed three times. It's frustrating because showing quick results on-the-go is a big part of my workflow with clients. Has anyone actually gotten it to work reliably? Or are we all just using the desktop version?
~Isla
~Isla
I've heard similar things from a few other users, Isla. It seems like the mobile experience hasn't quite caught up to the web platform yet, which is a real shame for workflows like yours.
To your question, I think most people I've spoken to are indeed defaulting to the desktop version for anything that needs to be reliable. I'd be interested to know what device and OS version you're using, as that can sometimes make a difference with these persistent crash issues. Have you found any workaround that helps, even temporarily?
Reviews build trust.
> "I'd be interested to know what device and OS version you're using"
Yeah, that's a good point. I've seen a few folks on an older Android version (like Android 11) getting crashes that don't happen on newer ones. Might be a rendering issue with the video decoder they're using.
I don't have a workaround for the app itself, but I've started pre-processing clips on desktop before leaving the office - just trim and export ready-to-share versions. Then I can upload those directly to the web platform from my phone's browser. Not ideal for "on-the-go" work, but saves me from the app's tantrums.
Have you tried clearing the app cache or reinstalling? I know it's the obvious suggestion, but sometimes that buys you a few stable sessions.
Clean code, happy life
> I think most people I've spoken to are indeed defaulting to the desktop version for anything that needs to be reliable.
This is the only reliable workaround. I've seen teams give up entirely and just implement a policy: mobile is for review only, never for creation or export.
The core issue is likely their mobile error handling. They're failing to gracefully degrade when a device decoder chokes, which a simple circuit breaker in the export pipeline would fix. Until they fix that, the crash cycle is guaranteed.
What's the SLO for a functional mobile export? For us, if it's below 99%, it's a blocker and we disable the feature. Opus Clip should consider the same.
Five nines? Prove it.
> "The core issue is likely their mobile error handling."
Yep. Seen it a dozen times. Mobile teams treat the decoder as a reliable service, not the flaky hardware abstraction it is. No retry logic, no fallback to software decoding, no circuit breaker. It's a guaranteed crash loop.
Setting an SLO is the right call. 99% is generous. If they're not measuring mobile export success rate as a key metric, they're just shipping bugs.
Prove it.
The mobile app failure rate is what finally got me to automate a desktop-only pipeline for our team. We set up a Jenkins job that clips, exports, and pushes to a shared drive when a source video is uploaded. Then the mobile app is only used for notifications.
It's a workaround, but it's reliable. If Opus Clip's mobile export SLO is as bad as you're seeing, you should treat the app as a viewer only and push your actual work upstream to the web platform via automation.
Build once, deploy everywhere