Closed
Bug 830204
Opened 12 years ago
Closed 7 years ago
When a 3rd party app update successfully finishes updating an app, notify the user that the update was successful
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(b2g18-)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
b2g18 | - | --- |
People
(Reporter: jsmith, Unassigned)
Details
(Whiteboard: [UX-P?])
Build: B2G 18 1/13/2013
Device: Unagi
Steps:
1. Update a 3rd party app successfully with no errors
Expected:
We should get a notification of confirmation that the update was successfully applied.
Actual:
The notification disappears with no user confirmation that the update was successful. This creates an awkward situation for the user where they do not truly understand if the update was or wasn't successful, as the result of the update was silent, which makes the results of the update appear ambiguous.
Reporter | ||
Updated•12 years ago
|
Blocks: b2g-app-updates
Reporter | ||
Updated•12 years ago
|
tracking-b2g18:
--- → ?
Reporter | ||
Updated•12 years ago
|
Whiteboard: [UX-P?]
Comment 1•12 years ago
|
||
I was told this is a UX consistent behaviour: we don't want to tell the user things they can't act upon.
I was surprised by that at first too but this makes sense.
Comment 2•12 years ago
|
||
Josh - please re-nominate if this isn't by design and critical enough to fix in the v1.x timeframe.
Flags: needinfo?(jcarpenter)
Comment 3•12 years ago
|
||
We're open to visible tipping off the user to a successful update, so long as the cue is subtle. We're wary of being obnoxious about "positive confirmations", along lines of Windows telling me via pop up that I've successfully plugged in my USB key. We'd like to revisit app updates in general, post v1.0 / 1.0.1 / 1.1. This is on the docket for tracking.
Flags: needinfo?(jcarpenter)
Reporter | ||
Updated•12 years ago
|
Reporter | ||
Updated•11 years ago
|
No longer blocks: b2g-apps-v1-next
Comment 4•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•