If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Grid locations for apps in a SIM customization are incorrect if the SIM is inserted after the FTE

RESOLVED INVALID

Status

Firefox OS
Gaia::Homescreen
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: jsmith, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [systemsfe])

(Reporter)

Description

4 years ago
Build: 10/23/2013 Buri 1.2

STR

1. Follow https://wiki.mozilla.org/B2G/QA/Customizations#Build_Setup to setup your build without a SIM inserted
2. Complete the FTE
3. Power down device & insert a AT&T US SIM
4. Power on device and check homescreen grid layout

Expected

The homescreen matches the grid setup specified in variant.json for the AT&T US SIM - Facebook in first location on third screen, Accuweather in 7th location on second screen, and Poppit in 4th location on 2nd screen.

Actual

The homescreen grid apps for Poppit & Accuweather usually end up on the wrong grid location.
(Reporter)

Updated

4 years ago
blocking-b2g: --- → koi?
Whiteboard: [systemsfe]
The actual result is actually the expected result. The user story of bug 893807 was refined/changed from the initial one at the comment 0 to the final one at coment 3, as you can see at (https://bugzilla.mozilla.org/show_bug.cgi?id=893807#c3).

Closing this one as INVALID for now, feel free to reopen if there's anything else here.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

4 years ago
Those requirements are incorrect. I know working with content management directly that having the grid position correct is critical, as we have partner agreements that indicate where each app should be laid out.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Out of scope for 1.2 now.Hence moving to 1.3.

SIM card should be put in before turning on device.
blocking-b2g: koi? → 1.3?
(Reporter)

Comment 4

4 years ago
(In reply to Preeti Raghunath(:Preeti) from comment #3)
> Out of scope for 1.2 now.Hence moving to 1.3.
> 
> SIM card should be put in before turning on device.

Incorrect - this is part of a target 1.2 user story. And it's a requirement by content management.
blocking-b2g: 1.3? → koi?
User Story in bug 893807 comment 3 was defined because of a product decision, we are past feature freeze for version 1.2, so it is not time to modify or add a User Story for version 1.2. Of course a new User Story can be created for version 1.3 to define a new kind of behavior, but for version 1.2.
Status: REOPENED → RESOLVED
blocking-b2g: koi? → ---
Last Resolved: 4 years ago4 years ago
Resolution: --- → INVALID
(Reporter)

Comment 6

4 years ago
(In reply to Marcelino Veiga Tuimil [:sonmarce] from comment #5)
> User Story in bug 893807 comment 3 was defined because of a product
> decision, we are past feature freeze for version 1.2, so it is not time to
> modify or add a User Story for version 1.2. Of course a new User Story can
> be created for version 1.3 to define a new kind of behavior, but for version
> 1.2.

Then we need to back that feature out. The grid location is critical to be correct and not up for negotiation via content management.
Status: RESOLVED → REOPENED
blocking-b2g: --- → koi?
Resolution: INVALID → ---
That was a product (isn't that the same as content management) and UX decision, not a development and QA one. The reasoning behind this behavior is that after the ftu has ended (after the first boot) the user might have personalized his grid before installing the SIM, and if so it would be a horrible UX to change his grid positioning. 

Since for some distribution the app placement may be critical, that's why we have a build time option that forces the SIM to be present before finishing the FTU. In fact is quite probable than our own build will have this flag set to true so the first grid the user sees is the correct one. But that's a decision that the OEM/operators can make. If they choose not to, that's their prerequisite too and then they accept that the user will have a personalized grid when he finally inserts the SIM. 

As I said this was not a dev decision, but I for one agree with product and UX on this one. Changing the users grid would be unacceptable for most users. 

Not going to continue the invalid/reopened dance, but I also think this is invalid. Amongst other things because the behavior implemented is exactly the behavior described at the user story. So if we want to change it, it should be a new user story. 

Can we get input from the ellusive content team here maybe?
s/their prerequisite/their prerogative. Hate writing from the phone sometimes.
(Reporter)

Comment 9

4 years ago
(In reply to Antonio Manuel Amaya Calvo (:amac) from comment #7)
> That was a product (isn't that the same as content management) and UX
> decision, not a development and QA one. The reasoning behind this behavior
> is that after the ftu has ended (after the first boot) the user might have
> personalized his grid before installing the SIM, and if so it would be a
> horrible UX to change his grid positioning. 

I get the fact a user can personalize their homescreen after the fact.

> 
> Since for some distribution the app placement may be critical, that's why we
> have a build time option that forces the SIM to be present before finishing
> the FTU. In fact is quite probable than our own build will have this flag
> set to true so the first grid the user sees is the correct one. But that's a
> decision that the OEM/operators can make. If they choose not to, that's
> their prerequisite too and then they accept that the user will have a
> personalized grid when he finally inserts the SIM. 

I don't think that's optional - that needs to be a requirement by default. Every single country we ship FxOS in per Karen requires a content grid with apps in specified locations. There's no such thing as a "this might work only if the SIM is provided before the FTE." This is a firm partner requirement with agreements with every app involved on that homescreen.

> 
> As I said this was not a dev decision, but I for one agree with product and
> UX on this one. Changing the users grid would be unacceptable for most
> users. 

I can agree that flipping around the grid is probably not the right approach. But we shouldn't get into this state in the first place if we have partner agreements in every country we ship FxOS in to require apps to be in certain grid locations.

> 
> Not going to continue the invalid/reopened dance, but I also think this is
> invalid. Amongst other things because the behavior implemented is exactly
> the behavior described at the user story. So if we want to change it, it
> should be a new user story. 
> 
> Can we get input from the ellusive content team here maybe?

There's an email thread started on this. I'll add you to it.

Given this bug probably isn't the right behavior per your clarification, I'll close this out. But I'm opening another bug to fix the default for SIM required on FTE.
Status: REOPENED → RESOLVED
blocking-b2g: koi? → ---
Last Resolved: 4 years ago4 years ago
Resolution: --- → INVALID
(Reporter)

Comment 10

4 years ago
I filed bug 930596 to address the concern I have.
You need to log in before you can comment on or make changes to this bug.