Canva App Ignores System Haptic Settings, Draining Battery
Canva's mobile app forces haptic feedback even when the user has disabled haptics system-wide and app-specifically. This disregards user preferences and causes unnecessary battery drain. Vendor bug rather than a market gap.
Signal
Visibility
Sign in free to unlock the full scoring breakdown, root-cause analysis, and solution blueprint.
Sign up freeAlready have an account? Sign in
Deep Analysis
Root causes, cross-domain patterns, and opportunity mapping
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Solution Blueprint
Tech stack, MVP scope, go-to-market strategy, and competitive landscape
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Similar Problems
surfaced semanticallyCanva Notification Settings Are Hard to Configure
A Canva user finds the controls for when not to be notified confusing and calls for a redesign. A single review, vendor-specific.
In-App Feedback Prompts Interrupt Active Design Work at Critical Moments
Canva triggers feedback popup surveys during active design sessions without respecting user context or workflow state. The interruption breaks creative focus at exactly the moment users are most engaged. No option exists to suppress or schedule feedback requests to less disruptive moments.
Trello Mobile Haptic Feedback Cannot Be Disabled
Trello's mobile app provides no in-app control for haptic feedback, requiring users to disable vibrations system-wide to stop it.
Canva mobile app shows false unread badge counts repeatedly
Canva users report phantom unread notification badges that disappear when the app is opened, happening multiple times daily. The gap is minor UX noise in a third-party product rather than an unmet market need. Low frequency and no willingness to pay for a fix.
Canva notifications silently fail to deliver for over a year
A Canva user reports notifications have not worked for over a year despite correct settings, forcing manual checking. The long duration and workspace-wide impact suggest a persistent platform bug rather than a one-off glitch.
Problem descriptions, scores, analysis, and solution blueprints may be updated as new community data becomes available.