Please report any other irregularities here.
We want to add a classifier page to the firefox os feedback form. This tracker covers that work.
Things that probably need to happen: 1. get a list of classifiers the user can choose from 2. figure out the ui--what should the page look like? 3. create a db column to store the information in -- we probably want something that's easy to query, but malleable. right now it's one class per feedback response, but, i could easily see this used in the future as a more general tagging system for responses. need to figure out the actual requirements, how it's going to be used and then decide on how to implement then. 4. make the changes to the ui -- need to make sure the classifier options are translatable; this has to be done in a separate branch so we can push the new strings to verbatim and wait for the required locales to be fully translated I'll create relevant bugs for the work involved and mulling over this list a bit.
Making this a P1 for 2014q1.
Priority: -- → P1
Target Milestone: --- → 2014Q1
Categories we want: * Media (photos, music, radio, videos) * Communication (SMS, dialer, contacts, email) * Other apps (browser, clock, maps, games, calendar, notifications) * Marketplace (Facebook, Twitter) * General device feedback (settings, performance, bluetooth, wifi, keyboard, screen, cost control, updates, battery) * Other (price, Mozilla, privacy, issues with the carrier) (We may need to work on strings here) Question phrasing: Which of these categories best describes what you're giving feedback about:
(We discussed this in IRC, but regurgitating it here for centralization purposes.) The Firefox OS feedback form has a lot of pages/questions. One thing I've been trying to do is make any option questions easy to get through. So you touch the option you want and that selects the option and moves you to the next page. Further, any options that are likely to stay the same get saved locally so they're automatically entered the next time. This adds a new option page. In order to make it work so that the user touches one thing to move on, we need to minimize the text/options so that they all fit on one screen. We'll need to do some word-smithing of those categories so that they're one-word each, all of them fit on one screen and they're self-explanatory. Otherwise we'll probably get a lot of Other choices. If we can't get the list of words to that point, then we'll have to figure out some different UX so that it's easy to get through. Also, Cheng mentioned that we're mot keeping track of whether people drop off the form before completing it and at what point. If we want to do that to measure changes like the one in this bug, then that'll need to be a separate bug. I'm not entirely sure how to do that offhand--it'll require some thought.
Wordsmithed categories (still open for debate): * Music, pictures, video * Calls, text and communications * Other apps that came with your phone * Apps and Marketplace * General comments about the device * Comments not about the device If that's still too long, we could use the following where we have a one word in a larger text and a description in smaller font: * Media (photos, music, videos) * Communication (texts, phone, contacts and email) * Built-in apps (web, clock, calendar, maps) * Marketplace (apps that you can buy or install) * Device feedback (anything about the phone or software itself) * Other (anything about the carrier or Mozilla in general)
Tweaking the title and making this block on the bug to measure drop-off.
Depends on: 969519
Summary: [tracker] add classifier page to firefox os feedback form → [tracker] add classifier page to Firefox OS feedback form
Bumping this to 2014q2 and making it a lower priority. This may or may not happen in quarter 2 depending on whether we figure out the things that need figuring and whether there's still time in the quarter to do the work.
Priority: P1 → P3
Target Milestone: 2014Q1 → 2014Q2
I'm not sure where this is at priority-wise anymore. Regardless, it's not a 2014q2 goal.
Target Milestone: 2014Q2 → ---
Pretty sure we're never going to do this, so I'm going to nix it now.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.