694163 - [NativeUI GA] create admin tool to manage /platforms content

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect)

Description

[Jaclyn Fu]

Attachment: User facing

As more devices become compatible with Firefox, we'd like to make the /platform page more user-friendly and admin-friendly. Since having a supported phone is key for a great Firefox experience, let's try to make it as easy as possible for users to find out if their device is compatible, and for us to easily update the page. 

Please find attached sketches.  Also for inspiration: http://www.opera.com/mobile/download/pc/

Requirements for user-facing site:
*Overview of Android system requirements at top
*If phone is not supported, provide brief explanation or where to get support on bottom
*Desired flow: Tablet/Phone > Manufacturer > Model > Image of model and other possible device names 
*Also looks great viewed from mobile devices 


Requirements for admin-facing site:
*Check box for either phone or tablet category
*Drop down list of manufacturers, with option to add new
*Input field for model name/number
*Upload field for image of device
*Input field for optional notes (e.g other device names) 

Feel free to provide suggestions.  Would like to have this by early Q1 2012.

Thanks!

Comment 1

[Jaclyn Fu]

Attachment: admin-facing

Comment 2

[mcbmoz]

Comment on attachment 566646 [details]
admin-facing

Jaclyn,

The image is showing up as:

Û\g’í$c	íŠHf62*E_—)MK·ŽµÆzC9Ç4þƒŽMŽ´.9<f“¤œôæœ
Þ”œÔ‡š8x'ó `
T}.ضè–Íë`ß=?JM.¢:ÕxåaùÔRÙÅ&æG9;”ô$c?\
åöêvÜÇ,WJ;7îßúƒúUˆüDöÄÈ僶e\©ÿ�

Can you repost? If you have trouble, email me the file and I'll help.

Comment 3

[Jaclyn Fu]

Attachment: updated_admin facing

Comment 4

[mcbmoz]

(In reply to Jaclyn Fu from comment #3)
> Created attachment 566660 [details]
> updated_admin facing

Jaclyn,

Per comment 3, can you answer a few more questions that will help inform next steps:
	
*What does the image in comment 3 represent?

*Who are the users? What kind of support will they require?

*Are managing photos of devices a Phase 1 or 2 for this tool and does it make sense to build in that level of complexity? (who will be formatting these images or do you want a script to autoresize, which can be helpful, but isn't always perfect)

*Should there be a filter to search by US, Europe, etc.? What would those filters be?

*When a device is retired what is the desired flow for eliminating that device from the tool

*Approximately how many manufacturers will there be? (this helps us in determining how a dropdown might function)

*What kind of information should go into the area called optional?

*How do you envision an admin coming to the site to search for a device before she or he adds it to the database? What would that look like?

Thanks for helping me better understand some of the needs behind the idea here.

Comment 5

[mcbmoz]

Ping on replying to comment 4 - let me know Jaclyn.

Comment 6

[Jaclyn Fu]

Hey Chrissie - sorry for the delay.  Will provide comments in the next couple of days. Thanks!

Comment 7

[Jaclyn Fu]

(In reply to mcbmoz from comment #4)
> (In reply to Jaclyn Fu from comment #3)
> > Created attachment 566660 [details]
> > updated_admin facing
> 
> Jaclyn,
> 
> Per comment 3, can you answer a few more questions that will help inform
> next steps:
> 	
> *What does the image in comment 3 represent?

This will be the view that admins see when they add new devices onto /platforms. 1) Check box to categorize whether added device is phone or tablet 2) A drop down list of device manufacturers with an option to add new manufacturer 3)Device model name 4)Upload image of device (or use a URL?) 5) Optional to add notes or other other international model names 
> 
> *Who are the users? What kind of support will they require?

The admin users are those who are filing bugs to add the new devices (Aaron? Tony?). Can you clarify what you mean by "what support they will require"? 

The people who go to our user-facing /platforms site are searching to determine whether their device is compatible with Firefox. They probably need support in terms of an explanation if their device is not compatible (SUMO article link on bottom?)
> 
> *Are managing photos of devices a Phase 1 or 2 for this tool and does it
> make sense to build in that level of complexity? (who will be formatting
> these images or do you want a script to autoresize, which can be helpful,
> but isn't always perfect)
> 
This should probably be a Phase 2. It would be great for users to know what the phone looks like, since sometimes there are multiple names for the same device. Let's revisit after Phase 1.

> *Should there be a filter to search by US, Europe, etc.? What would those
> filters be?

I don't this this is necessary - Irina feel free to chime in. 
> 
> *When a device is retired what is the desired flow for eliminating that
> device from the tool

I imagine there to be a profile-esque entry for each phone when details need to be edited. So the admin-user will click on the device -> phone details will show -> option to edit or delete.  Aaron/Tony - is there also something else that would help your process? 
> 
> *Approximately how many manufacturers will there be? (this helps us in
> determining how a dropdown might function)

Right now it's about ~15, I don't think it's going to fluctuate too much around there since it's mainly devices, not manufacturers, that change. 
> 
> *What kind of information should go into the area called optional?

Other international names for the device (if any), or if there are any other notes the admin wants to include about the device
> 
> *How do you envision an admin coming to the site to search for a device
> before she or he adds it to the database? What would that look like?

I'm not sure if I am understanding this question correctly. I would envision the admin site to have the same list of already added devices.
> 
> Thanks for helping me better understand some of the needs behind the idea
> here.

Thanks!

Comment 8

[Irina Sandu]

Aaron pointed out to me yesterday that the new native Fennec might work with additional ARMv6 devices, which would expand the list of supported devices when it comes out. I think Engineering is still investigating this, but it is good to keep in mind that we might need this page reformatted by the time that version comes out.

Comment 9

[Kohei Yoshino [:kohei]]

(In reply to Jaclyn Fu from comment #0)
> *If phone is not supported, provide brief explanation or where to get
> support on bottom

+1

I'd like to see non-supported devices. People cannot understand his/her device is not tested nor supported if it's not on the list. FYI, our Japanese localized page shows both supported and non-supported devices sold in Japan:

http://mozilla.jp/firefox/mobile/platforms/

On the admin face: how about using the Google Spreadsheets API? I have never used it but the device compatibility data has been collected up on a spreadsheet. It's worth a try, I guess.

http://code.google.com/intl/en/apis/spreadsheets/

https://docs.google.com/spreadsheet/ccc?authkey=CPiPp9IK&key=0AhE7m4JB2j6tdEJFZ3NoZkRoRTM3TTRpQll3UjZLYnc#gid=3

Comment 10

[Irina Sandu]

(In reply to Kohei Yoshino from comment #9)
> (In reply to Jaclyn Fu from comment #0)
> > *If phone is not supported, provide brief explanation or where to get
> > support on bottom
> 
> +1
> 
> I'd like to see non-supported devices. People cannot understand his/her
> device is not tested nor supported if it's not on the list. FYI, our
> Japanese localized page shows both supported and non-supported devices sold
> in Japan:
> 
> http://mozilla.jp/firefox/mobile/platforms/
> 

I think that might be a bit tricky, to show all of the unsupported devices, because there are a lot of them (between 300 and 400 atm; and the number is growing). What we could do is aim to cover the top ones, say the top 50 models or so.

Comment 11

[Kohei Yoshino [:kohei]]

Here's a sample API query:
https://spreadsheets.google.com/feeds/list/0AhE7m4JB2j6tdEJFZ3NoZkRoRTM3TTRpQll3UjZLYnc/2/private/full

Comment 12

[Jaclyn Fu]

The gDoc solutions sounds interesting - does anybody know if it's do-able? 

Agreed on not showing the list of unsupported devices, because 1) it's a lot of devices and 2) we should focus on pros than cons 

ping on timeline and anything else needed to get started?

Comment 13

[mcbmoz]

(In reply to Jaclyn Fu from comment #12)
> The gDoc solutions sounds interesting - does anybody know if it's do-able? 
> 
> Agreed on not showing the list of unsupported devices, because 1) it's a lot
> of devices and 2) we should focus on pros than cons 
> 
> ping on timeline and anything else needed to get started?

Jaclyn, this is a little late for getting into Q4, but why don't you take the information you've gathered from my questions around functionality and Kohei's recommendations and produce a brief similar to what Laura M. has done for the 3.6 Colbert/Stewart campaign idea.

Then, attach for the team to evaluate and we'll work on a build plan for Q1 2012.

Comment 14

[Jaclyn Fu]

Hi Chrissie,

Please find brief here: https://docs.google.com/document/d/1K6Okh0p8M3tg6FGlUGQqkO_6pNLlbF53tveBCOcj3xY/edit

Please let me know if you have any questions or if we should walk through the necessary bugs and next steps together

Thanks!

Comment 15

[mcbmoz]

Assigning to Mike Alexis to find webdev resources, the website team doesn't have backend bandwidth to build this at this time :-(

Comment 16

[Jaclyn Fu]

Hey Mike - will this be funneled into the list for Q1 projects?

Comment 17

[Jaclyn Fu]

Ping Mike - we received news yesterday that ARMv6 devices are very likely to be compatible with the native UI build at launch. To prepare for the addition of all these new devices, we would really like this page to be ready by March.  

Also free to chat to hash out details - thanks!

Comment 18

[Aaron Train [:aaronmt]]

(In reply to Jaclyn Fu from comment #17)
> Ping Mike - we received news yesterday that ARMv6 devices are very likely to
> be compatible with the native UI build at launch.
That's news to me. Who mentioned this?

Comment 19

[Jaclyn Fu]

Johnath mentioned it in a meeting yesterday - it's not a priority, but people are going to start working on it

Comment 20

[mcbmoz]

(In reply to Jaclyn Fu from comment #19)
> Johnath mentioned it in a meeting yesterday - it's not a priority, but
> people are going to start working on it

Hey Jaclyn, can you give a little more context to what people are going to start working on in comment 19 - thanks!

Comment 21

[Jaclyn Fu]

Getting Firefox onto ARMv6 devices after native UI launches

Comment 22

[mcbmoz]

Goal: Build a content management tool for Mozilla's mobile team to add and delete devices that are shown on the /platforms consumer-facing page.

----

Deadline: April 17, 2012

----

Final requirements:

The following fields should be covered for the admin-user (e.g. Aaron Train and Tony Chung represent the users)

Add new device:
-Name of Device (text field)
-Phone or Tablet (radio button)
-Manufacturer (e.g. Samsung)
-Model (e.g. Galaxy Tab 10.1)
-Country (dropdown)

Delete old device - single action to remove device

Output = if the user can locate the device "Hooray! You can download Firefox!"

(for this phase, we are not including a "No, this device is not compatible" but will think on how to do this in a future phase)

Consumer-users will search for this using the following fields:
-Phone or Tablet (dropdown or radio button)
-Name of device (dropdown -> pulls model information)
-Manufacturer (e.g. Samsung)

(Note: for this phase we will not reveal the Country field until we have critical mass of editorial information)

Alright, Mike A. we're ready to meet with WebDev and kick this off for early Q2 deployment.

Comment 23

[Mike Alexis [:malexis]]

Notes from requirements discussion:

GUI would be ideal and possible to do in django, but don't have database ready and would take too long given the timeline. down the road we can do it right. 

We'll use flat text file with 5 lines, automatically generate tempate clicking edit in github, make changes. creates admin-like experience.

Relatively simple to implement -- 1-2 days for coding, documentation, testing.

Does "edit this file" create its own branch? need to confirm.

Front end redesign happening. design shouldn't block the developement. Can use what's currently on the page.

Mobile platform page is in the first tier of pages to be migrated to bedrock.

Comment 24

[James Long (:jlongster)]

1.13 isn't a valid milestone, the next one is 2.0 which is in April.

Comment 25

[Fred Wenzel [:wenzel]]

James, please coordinate with Steven if he's the one to port the frontend portion of this.

Comment 26

[James Long (:jlongster)]

(In reply to Fred Wenzel [:wenzel] from comment #25)
> James, please coordinate with Steven if he's the one to port the frontend
> portion of this.

Ok, putting this in the 2.0 milestone which is the next PHP one to remind me. I'll work with Steven on this after we get the major parts of the Python port done.

Comment 27

[Jaclyn Fu]

Hey malexis - are you going to be opening a fresh new bug for this or are we keeping this thread? Thanks!

Comment 28

[Mike Alexis [:malexis]]

hi Jaclyn,
decided to keep this bug but we need to be mindful that the thread begins at comment#22. Previous comments are invalid.

Comment 29

[Fred Wenzel [:wenzel]]

Unassigning bugs from James that are not migration-related bedrock platform bugs. Let me know if you have any questions.

Comment 30

[Jaclyn Fu]

Quick ping on progress - Do we have an update on where this is? Thanks!

Comment 31

[Mike Alexis [:malexis]]

Steven, can you check out comment#22 and comment#23 and see if this is something you can tackle? James can provide guidance.

Comment 32

[Steven Garrity [:sgarrity]]

Jacklyn, The fields that Chrissie proposed in comment #22 were:

> -Name of Device (text field)
> -Phone or Tablet (radio button)
> -Manufacturer (e.g. Samsung)
> -Model (e.g. Galaxy Tab 10.1)
> -Country (dropdown)

Is the "Name of Device" not just "Manufacturer + Model"? Also, how does "Country" work? Aren't many devices available in many countries?

Comment 33

[Jaclyn Fu]

Manufacturer + Model is same thing as name of device

Country: some phones are called something different in other countries. Is there a way to note other possible device names?

Comment 34

[Steven Garrity [:sgarrity]]

We've got a basic start on this, with the devices reading out of a simple text file. Will update shortly.

Comment 35

[Steven Garrity [:sgarrity]]

We've got a version of this page built out in Bedrock that builds the list of devices from a static text-based CSV file.

Pull request: https://github.com/mozilla/bedrock/pull/128

You can see the text file here: https://github.com/sgarrity/bedrock/blob/70279990734cff5066f922885402943e355af691/media/devices.csv

We had to take some liberties with text/layout in porting to Bedock, but these can be reviewed once we've got it staged in dev.

Comment 36

[[github robot]]

Commits pushed to dev at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/70279990734cff5066f922885402943e355af691
Mobile Firefox compatability page powered by CSV file

https://github.com/mozilla/bedrock/commit/06cabf4d0e1bd886f82d0f808924abf64fa72def
Merge pull request #128 from sgarrity/bug-694163-platforms

Bug 694163 platforms

Comment 37

[Steven Garrity [:sgarrity]]

Going to close this bug and track the implementation of the new page over in Bug 751632.