Closed Bug 1487764 Opened 8 years ago Closed 7 years ago

Screenshot Go - 1st SUMO page

Categories

(support.mozilla.org :: Knowledge Base Content, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wehuang, Unassigned)

Details

Attachments

(6 files, 4 obsolete files)

Hi Joni: As previously discussed in mail I put the relevant Screenshot Go (renamed from "Screenshot Plus") stuff here for your reference to design the SUMO KB article: 1. The apk. You can download today's apk "v1.0(152).nightly", copy it to your phone then install. The download page is: https://app.bitrise.io/artifact/7848128/p/0d8d293b803410525b4716b0eb646f5c Sorry we are still working with Releng to set up the nightly distribution via Google Play Store, so at this moment it takes few mores step to get the app installed. I'll keep you updated once the nightly is ready so you can easily get the latest update from Google Play Store. 2. since the apk is still under development I also attached the link to our latest UX spec for your reference. Feel free to let us know shall you have any question about the design, we can also have vidyo for that if preferred. The Spec link is: https://mozilla.invisionapp.com/share/24N3MMQB986#/screens/310133903 3. The logo. As we just confirmed the new product name this week, it takes another 2~3 weeks for the branding team to design the logo (current ETA Sep. 14th) so it's currently unavailable. I hope this won't be a problem for your article design but let me know if it is. 4. Confirmed we'll need the in-app URL like Rocket, is it something we will get earlier (e.g., once your English KB article is ready, maybe?) so can put it in our App? Thanks!
Attached file app-preview-release-unsigned.apk (obsolete) —
also attached the apk directly as well. (from the link of bullet#1 above)
Flags: needinfo?(jsavage)
Thanks for the APK and updates, Wesly. Here's a link you can use in the product: https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/screenshot-help Where are you linking from? Will it make sense for us to link to the Screenshot Go category so people can choose an article, or should we link to a single article?
Thanks, Joni! 1. We'll integrate the URL into "Settings-->About-->Support" of the App, like the page 25, screen H in the UX spec[1]. I'm not sure if we'll be listed in https://support.mozilla.org/ but I believe most of the case the users will link from the App. 2. Not sure if I really get the meaning of "Screenshot Go category" and "a single article". Is Rocket the later? I think to follow what Rocket does is a good way to go. In the meantime since this is an experimental product at this moment, we could consider constructing the SUMO pages in the minimum scope while keeping the flexibility for scaling in the future (e.g., when we get huge user, become a confirmed product, and grow the features). Please let me know if we should go deeper into this. Joe, would you like to chime in? [1] https://mozilla.invisionapp.com/share/24N3MMQB986#/screens/310133927
Flags: needinfo?(jcheng)
Attached file app-go-debug.apk (obsolete) —
btw I updated the apk attached, please use this "app-go-debug.apk" instead of the previous one (which may lead to installation fail)
Attached file app-go-debug.apk (obsolete) —
set the previous apk obsolete.
Attachment #9005618 - Attachment is obsolete: true
Attachment #9005975 - Attachment is obsolete: true
what you said makes sense Wesly. Going with what we did in Rocket and with a minimum scope makes sense. Thanks
Flags: needinfo?(jcheng)
Thanks, Wesly. I tried installing the APK from comment #5 but it wouldn't install on my Pixel. Is there another file?
Flags: needinfo?(jsavage) → needinfo?(wehuang)
Attached file app-go-debug-175.apk —
Sorry to hear that, I tried it before upload but anyway let me put a newer version here with more UI completion. It's the "app-go-debug-175.apk" (QA has completed the 1st run test with it) and I'll also let you know when nightly is ready (should be soon!)
Attachment #9005976 - Attachment is obsolete: true
Flags: needinfo?(wehuang) → needinfo?(jsavage)
Thanks, Wesly! I was able to install this new one now. I'll start drafting the article and will finalize it when I get Nightly.
Flags: needinfo?(jsavage)
I forgot to answer comment #3. Firefox Rocket is its own category and we have several articles for it: https://support.mozilla.org/en-US/products/firefox-rocket/get-started I can write a minimal one-pager for Screenshot and hide it from the home page (people can just get to it from the in-product link. Do you plan to have a logo? I will still need a logo or else it will show the nurse photo shown here: https://support.mozilla.org/en-US/products/screenshot-go If you don't plan to have a logo, I can put the Screenshot Go article in the Firefox Rocket category. It's not ideal but we can move it out once it becomes confirmed as a product.
Flags: needinfo?(wehuang)
I've drafted a one-pager. The direct link is here but the link I gave in comment #2 will automatically redirect to it: https://support.mozilla.org/kb/screenshot-go-capture-and-organize-screenshots Once I have Nightly, I will finalize the article with any edits and images and send it off to L10N. As I mentioned in comment #10, we'll need a logo so the nurse image won't show up on the page, or I can use the same logo as Rocket if you think that's a good idea.
Per Slack, here's the doc where the team can provide feedback: https://docs.google.com/document/d/1hpisBGMsSn_InoCDWVKebwuDEIyJeVo9QflHdVr92Jc/edit?usp=sharing Please provide any feedback by Sept. 18 if possible.
Thanks, Joni! (In reply to Joni Savage ("need info" me) from comment #10) > I can write a minimal one-pager for Screenshot and hide it from the home > page (people can just get to it from the in-product link. 1. the draft looks good to me! as discussed in Slack I'll follow with the team for their feedback by Sep. 14. 2. I believe "only get to the page via the in-product link" aligns the idea of starting from the minimum, but I'll add Joe to confirm from the product perspective @Joe would you share the view about Joni's suggestion? > Do you plan to have a logo? I will still need a logo or else it will show the nurse photo > shown here: https://support.mozilla.org/en-US/products/screenshot-go 3. yes we'll have our own logo and branding team is working on it (we saw the draft but it still needs some refinement), is this a blocker for l10n? are we able to add it to the page in the later phase? (still before open beta for sure) (In reply to Joni Savage ("need info" me) from comment #11) > I've drafted a one-pager. The direct link is here but the link I gave in > comment #2 will automatically redirect to it: > https://support.mozilla.org/kb/screenshot-go-capture-and-organize-screenshots 4. the direct link here works but the link in comment#2 leads me to an error page. I assume this is expected for now?
Flags: needinfo?(wehuang)
Flags: needinfo?(jsavage)
Flags: needinfo?(jcheng)
Great, I'll wait for the team's feedback before I mark for L10N. 3. The lack of logo isn't a blocker for L10N. We can still localize it and I can add the logo later; I'll just let the community know that the nurse logo will go away. 4. There isn't supposed to be an error page. Did you try it with the variables for OS, version and Locale plugged in?
Flags: needinfo?(jsavage) → needinfo?(wehuang)
(In reply to Joni Savage ("need info" me) from comment #14) > Great, I'll wait for the team's feedback before I mark for L10N. > > 3. The lack of logo isn't a blocker for L10N. We can still localize it and I > can add the logo later; I'll just let the community know that the nurse logo > will go away. > > 4. There isn't supposed to be an error page. Did you try it with the > variables for OS, version and Locale plugged in? Thanks Joni, 3 updates from me: 1. The team has gone through your draft and only get a minor suggestion in the Gdoc (have updated most of our previous comments), kindly take a look we can follow the discussion in the doc. 2. I simply clicked the URL in comment#2 so got error. With variables plugged in it works and we'll integrate it into our App. 3. We are very close to locking down the logo and I'll send it to you once done. Is there any preferred size and file format? (like .png?)
Flags: needinfo?(wehuang)
ni Chloe, who is our new Product Manager, for checking comment#13, too.
Flags: needinfo?(shichen)
(In reply to Wesly Huang (EPM) from comment #16) > ni Chloe, who is our new Product Manager, for checking comment#13, too. Hi Joni, nice to meet you. For comment#13, on top of getting to the page via the in-product link, we also would like to put it on the web page, just like Rocket does.
Flags: needinfo?(shichen)
Hi Joni: 1. We've replied to your comments in the GoogleDoc draft, kindly check it and we can follow there. 2. We got the logo file source today, is there any preferred size and file format (like 60*60 pixel, .png?) so we can tailor and attach here? Thanks! (In reply to Wesly Huang (EPM) from comment #15) > Thanks Joni, 3 updates from me: > > 1. The team has gone through your draft and only get a minor suggestion in > the Gdoc (have updated most of our previous comments), kindly take a look we > can follow the discussion in the doc. > > 3. We are very close to locking down the logo and I'll send it to you once > done. Is there any preferred size and file format? (like .png?)
Flags: needinfo?(jsavage)
96 x 96 pixel works best. Any image file format works too. Thanks!
Flags: needinfo?(jsavage)
Hi Joni: Attached the logo. Kindly note the app is still in the pre-Beta stage (open beta on Sep. 28) so the logo goes with "BETA". We'll need to update it when official launch (~early Oct.). Please feel free to let me know if you prefer another bug to track the logo replacement. btw for Chloe's comment#17, will you also help put this product on the web page, like Rocket? Thanks. (In reply to Chloe Chen from comment #17) > Hi Joni, nice to meet you. For comment#13, on top of getting to the page via > the in-product link, we also would like to put it on the web page, just like > Rocket does.
Flags: needinfo?(jsavage)
Attached image appicon_beta_96.png (obsolete) —
Thanks, Wesly. Looks good and I've already updated the article to reflect the new logo.
Flags: needinfo?(jsavage)
Hi Chloe, Nice to meet you. Do you mean put it on the home page (https://support.mozilla.org/)? We can definitely do that. What day should we make it visible on the home page? Should we wait until Sept 28 or on a different day?
Flags: needinfo?(shichen)
(In reply to Joni Savage ("need info" me) from comment #23) > Hi Chloe, > > Nice to meet you. Do you mean put it on the home page > (https://support.mozilla.org/)? We can definitely do that. > > What day should we make it visible on the home page? Should we wait until > Sept 28 or on a different day? Hi Joni, thanks for getting back to us. We are planning to make it visible by Sep. 28. Furthermore, we need to add "Beta" on this version to distinguish between the beta and the final GA version.
Flags: needinfo?(shichen)
(In reply to Joni Savage ("need info" me) from comment #22) > Thanks, Wesly. Looks good and I've already updated the article to reflect > the new logo. Sorry, Joni. We have slightly refined the logo color so would you help replace the logo with this newly attached one? Thanks. (I'll mark the previous one obsolete too)
Flags: needinfo?(jcheng) → needinfo?(jsavage)
Attachment #9010187 - Attachment is obsolete: true
btw I tried the direct link[1] but don't see any logo (ever saw the nurse icon before), maybe it's because it's not yet published? Anyway attached my screen fyi. [1] https://support.mozilla.org/kb/screenshot-go-capture-and-organize-screenshots
Sorry about that, Wesly. The missing logo was an unintended effect of our recent site redesign. I'm working with Madalina and Roland to fix it ASAP. (I'll upload the new logo that you've attached).
Flags: needinfo?(jsavage) → needinfo?(mana)
I've filed an urgent bug to fix the logo issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1494776
Joni, the last piece I see before resolving this bug: there is nurse icon used in the l10n page[1], would you help on it? Thanks. (the other thing is the logo size looks a bit small but it seems to be a general issue, as I see it happens in other product pages too) [1] https://support.mozilla.org/id/kb/kirim-data-penggunaan-anonim-dari-firefox-pada-per
Flags: needinfo?(jsavage)
Hi Wesly, I've uploaded a new logo to the article page so the nurse logo shouldn't appear anymore. As far as size goes, I'll share this feedback with the team. I believe we need to do a bit of testing to see if the logo needs to be resized.
Flags: needinfo?(jsavage)
Thank, Joni. Unsure if it takes some time to take effect but I still see the nurse logo even used F5 to force-refresh the page. Would you help check? Thanks. (In reply to Joni Savage ("need info" me) from comment #33) > Hi Wesly, > > I've uploaded a new logo to the article page so the nurse logo shouldn't > appear anymore. As far as size goes, I'll share this feedback with the team. > I believe we need to do a bit of testing to see if the logo needs to be > resized.
Flags: needinfo?(jsavage)
As per bug 1494776, product logo issue has been fixed, i'm clearing my needinfo
Flags: needinfo?(mana)
Hi Wesly, I no longer see the nurse logo. Do you still see it?
Flags: needinfo?(jsavage)
Yes, I still see the nurse logo on this page, and unsure if there is something wrong only for me? https://support.mozilla.org/id/kb/kirim-data-penggunaan-anonim-dari-firefox-pada-per
Attached image nurse logo.png —
Flags: needinfo?(jsavage)
Thanks for catching this. I've fixed it now so it should show the privacy logo. This article applies to all of mobile, not just ScreenshotGo
Flags: needinfo?(jsavage)
thanks Joni!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: