862262 - [MMS][User Story] Message Expiry

Status: RESOLVED DUPLICATE of bug 868218

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[Kai-Chih Hu [:khu]]

MMS messages might come with a relative expiry time period. Retrieving an expired message results in a generic error returned to content page. Should we expose this field to content so that UX may define behaviours for such messages? 

This is for MMS only, and this is used for manual retrieval mode. Sender won't know when the MMS will be expired, but the recipients know. 

Should we implement this feature? Thanks!

Comment 1

[Maria Angeles Oteo (:oteo)]

Checking the specs, I've not seen any special requirement about it, so I would avoid implementing this feature

Comment 2

[Alex Keybl [:akeybl]]

Minusing given comment 1

Comment 3

[Peter Dolanjski [:pdol]]

Kevin, what happens now in the event that the MMS is expired and the user attempts a download of the attachment?

Comment 4

[ayman maat :maat]

Hi Maria / Peter

I think form a UX perspective we are going to need this. If an undownloaded MMS has a 'shelf life' and the user attempts to manually download the message after this 'shelf life' has expired we need to inform them that the message cannot be received as it has expired and therefore been deleted.

Comment 5

[Vicamo Yang [:vicamo][:vyang]]

(In reply to Peter Dolanjski [:pdol] from comment #3)
> Kevin, what happens now in the event that the MMS is expired and the user
> attempts a download of the attachment?

We have alreadt handle message expiry in Gecko. A generic error is returned upon trying to retrieve a already expired message.

Comment 6

[Peter Dolanjski [:pdol]]

Given Vicamo's description, it sounds like this can be handled by ensuring that the error strings are clear.  Ayman, would that suffice from a UX perspective?

I would be happy to have this handled in new UX if risk is not increased with the added scope.

Comment 7

[ayman maat :maat]

Attachment: HTML5_SMS-MMSUserStorySpecifications_20130429_V7.0

Case covered in wireframe pack:
HTML5_SMS-MMSUserStorySpecifications_20130429_V7.0
page 44

let me know if you require more information

Comment 8

[ayman maat :maat]

With reference to #comment 4 nominating for leo+

Comment 9

[Dietrich Ayala (:dietrich)]

Maria, please re-evaluate per Ayman's most recent comments.

Comment 10

[Maria Angeles Oteo (:oteo)]

I agree with Ayman's proposal, I just only commented that I didn't see any specific requirement about it in Telefónica spec but if it's feasible and important from the User experience point of view, let's go for it!

Comment 11

[Corey Frang [:gnarf]]

I made a bug to deal with all of these expiry based messages according to Ayman's latest wireframes - It includes the "past the expiration" message

Comment 12

[Wayne Chang [:wchang]]

Triage - Leo+. Duplicate of a Leo+ bug also.