Closed Bug 1067614 Opened 10 years ago Closed 10 years ago

[User Story] Ensure users are always on the latest loop mobile version

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: oteo, Assigned: crdlc)

References

Details

(Whiteboard: [mobile app][loop in v1.1][loop approved for 1.1][blocking])

User Story

As a user, when launching Loop mobile app, I will be notified that I can NOT use it in if I have an installed version lower than the one available in the Market Place.

- This message will be shown when launching the application after the successful FxOS version and Device compatibility checking (bug 1087797).
- After that, we will check the Loop version installed in the device with the version available in the Market Place. If they are different the confirmation screen to Download the latest Loop app will be offered.

TokBox is going to guarantee backwards compatibility only for a limited set of JS library versions. Hence, if a user is using a FxOS Loop Mobile Application based on an unsupported library version, there is no guarantee of a proper Loop behavior.

For this Loop mobile 1.1 version, there is not an available API to check Tokbox SDK compatibility, that's the reason we need to force the updating with the latest version available in the Market Place.

Attachments

(1 file)

TokBox is going to guarantee backwards compatibility only for a limited set of JS library versions. Hence, if a user is using a FxOS Loop Mobile Application based on an unsupported library version, there is no guarantee of a proper Loop behavior. That's the reason we need Loop Mobile client to check if there is any available version update of the application when it starts, so that we can suggest the user to download and apply it as otherwise Loop application may not work properly.
Blocks: Loopmov_1_1
After talking with Product/UX team, and as there is not an available API to check Tokbox SDK compatibility, for this Loop mobile 1.1 version we will shown to the user a confirmation screen advising him to download from the Market Place the latest Loop version. This message will be shown when launching the application and after the successful FxOS version and Device compatibility checking (bug 1087797). After that, we will check the Loop version installed in the device with the version available in the Market Place. If they are different the confirmation screen to Download the latest Loop app will be offered: - Confirm BB: http://buildingfirefoxos.com/building-blocks/confirm.html - String: "Required update: There is an update with new features. Do you want to download it? This update is required to continue using Firefox Hello" with buttons "Download" and "Cancel" ((already included in bug 1084363)
Depends on: 1084363
Blocks: MP_Loop1.1
No longer blocks: Loopmov_1_1
Severity: normal → critical
Summary: Ensure users are always on the latest loop mobile version → [User Story] Ensure users are always on the latest loop mobile version
User Story: (updated)
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
Attached file Github pull request
Comment on attachment 8511867 [details] Github pull request Thanks friends
Attachment #8511867 - Attachment description: Github pull request (WIP) → Github pull request
Attachment #8511867 - Flags: review?(josea.olivera)
Attachment #8511867 - Flags: review?(carmen.jimenezcabezas)
Blocks: Loopmov_1_1
Comment on attachment 8511867 [details] Github pull request LGTM. r=me Left a few comments on the PR but there are some nits. Once you address them, please land at will. Thanks Cristian!
Attachment #8511867 - Flags: review?(josea.olivera) → review+
Comment addressed José, thanks
Comment on attachment 8511867 [details] Github pull request The patch LGTM, I left a few comments on the PR. Thanks Cristian
Attachment #8511867 - Flags: review?(carmen.jimenezcabezas) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
BE CAREFUL uplifting this patch to 1.1 because OptionMenu changed in master (I added this just for me XD)
Cristian, although QA team didn't have time to test it properly in master, let's uplift it to 1.1 branch (together with bug 1084363) and QA will verify it on that branch tomorrow.
Flags: needinfo?(crdlc)
Whiteboard: [mobile app][loop not in v1.1][loop approved for 1.1][blocking]
Flags: needinfo?(crdlc)
Whiteboard: [mobile app][loop not in v1.1][loop approved for 1.1][blocking] → [mobile app][loop in v1.1][loop approved for 1.1][blocking]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: