Open
Description
Project Status Overview
Project Objective:
Create comprehensive documentation, including examples, to guide teams building features in the mobile app on when to use native mobile app features, WebViews, or transition a user from the mobile app to an authenticated browser experience.
Key Areas of Guidance:
- Factors for PMs and Teams: Outline key factors for PMs and teams to consider when determining the optimal user experience. This includes assessing task frequency, performance needs, internet access requirements, native device functionality, accessibility, user experience consistency, and development resources.
- WebView Optionality: Explain the options for using WebViews, such as embedding customized webpages. Highlight how removing unnecessary elements like top URLs, navigation bars, and headers while retaining essential components like the footer can improve the user experience and help users complete tasks efficiently.
- Examples of Each Scenario: Include practical examples for each scenario to illustrate when to use native mobile app features, WebViews, and browser transitions. These examples will help teams better understand and apply the guidelines in real-world contexts.
By providing comprehensive guidance and practical examples, this documentation aims to help teams make informed decisions that optimize user experience and resource efficiency when developing VAHB features.
Product Brief:
- [link to GitHub Product Brief]
Monthly Update for Stakeholders
| Date | Progress & Key Accomplishments | Issues/Risks/Blockers |
|---|---|---|
| 8/5/24 | Not started | |
| 9/9/24 | Not started - expected to be picked up next sprint. | |
| 10/1/24 | Product started on framework | |
| 10/15/24 | Framework was sent to POs. Waiting on review from POs to determine next steps. | |
| 11/12/24 | POs have reviewed and approved the framework. However, a spike was conducted to determine whether SSO can work with browser links and it currently cannot. The Identity team is planning to explore this functionality at some point in the future. As a result, the documentation needs to be updated to reflect SSO only working for Webviews then uploaded to the doc site | |
| 11/19/24 | Framework has been uploaded to the doc site, making this epic complete. The doc should be continuously updated as more is learned about leveraging SSO and teams start building features using SSO in the mobile app |
Current Dependencies / Blockers
Blockers
| Blocker | Team / Owner | Est to Resolution |
|---|---|---|
| Internal dependency ? | ||
| External dependency ? |
Team Members
Contact List
VA:
- Mobile OCTO Product Leads: Rachel Han or Ryan Thurlwell
- VA OCTO Product Leads:
- External Team 1 & Role:
- External Team 1 & Role:
Ad Hoc:
- Mobile Team: Global, Health and Benefits, Design System, QA, API
- Mobile Team Lead:
- FE Engineering:
- BE Engineering:
- Design:
- Content
- QA:
- Mobile Teams that are involved: Global, Health and Benefits, Design System, QA, API
Activity