Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2.42 what's new content update #10272

Closed
3 of 16 tasks
dumathane opened this issue Nov 26, 2024 · 2 comments · Fixed by #10271
Closed
3 of 16 tasks

Release 2.42 what's new content update #10272

dumathane opened this issue Nov 26, 2024 · 2 comments · Fixed by #10271
Assignees
Labels
app store front-end Ticket requires front-end work global Issues for the global team

Comments

@dumathane
Copy link
Contributor

dumathane commented Nov 26, 2024

Description

As the Veteran, I want all the app stores/pages to accurately reflect the most recent changes in the app so that I know what to expect before going into the app.

As part of this story we want to:

Determine what, if any, changes are needed to Apple, Google and VA.gov App Store pages

  • App Store Whats New content(not applicable for VA.gov App Store)
  • App Store images
  • App Store app description needs updated

App Store What's New content changed to:

You can now view and download files from your claim in the app.

Link for content discussion.

Acceptance Criteria

Notes

  • All work to be done before the end of the sprint that the feature is going out
  • Some parts have a longer lead time (Va.gov App Marketing Page) so please prepare accordingly
  • Whats New In-App Alert box content is not included here as its not part of the app store - see separate ticket template "In-App Whats New Content - Feature Name - Release" ex 8833
  • Any questions please reach out to Release Manager

Images

  • Includes: iPad, iPhone and Android Phone (and a description image)
  • Process for Updating the App Stores
  • Historically - UX creates the images backed on this process then Flagship PM validates the images and then works with their FE to submit the PR to update the images
  • Images should be the same across Google, Apple and Va.Gov
  • UX to create a new folder with YYYY Mon and Feature in this Google Drive
  • Note if new feature is added then may need to consider how we list them in the first image which contains a list of features "Use this app to:"
  • Work is done outside of the Release Ticket process
  • As of June 2024 - new images need to be compressed through something like ImageOptim per Tim before being added into the repo to remove any metadata that might be bloating the files
  • Process doc for Update Va.Gov App Store

Content

  • Inclues: App Store Whats New and App Description
  • Content will create the test for Whats New App Store (if we do not want to use "We added general improvements and fixed a few bugs.")
  • This change is required for the Release process - notify Release Manager change is coming and when its done

Va.Gov Marketing Page

  • Its a VA Marketing Page that will need to be updated by Flagship PM and has its own process
  • Images need to be stored in Images in Use Github folder as VA pulls images from here

Ticket Checklist

  • Acceptance criteria defined
  • Labels added (front-end, back-end, feature)
  • Linked to an Epic
  • Notify Mobile Release Manager at least 1 sprint ahead of implementation date
@dumathane dumathane added app store front-end Ticket requires front-end work global Issues for the global team labels Nov 26, 2024
@dumathane dumathane self-assigned this Nov 26, 2024
@kellylein kellylein modified the milestones: v2.42.0, v2.43.0 Nov 26, 2024
@TKDickson
Copy link
Contributor

@dumathane @kellylein this ticket is complete already, right?

@dumathane
Copy link
Contributor Author

yup!

@dumathane dumathane linked a pull request Dec 5, 2024 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app store front-end Ticket requires front-end work global Issues for the global team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants