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

Developer options menu #46

Open
BenHenning opened this issue Aug 2, 2019 · 1 comment
Open

Developer options menu #46

BenHenning opened this issue Aug 2, 2019 · 1 comment
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Priority: Important This work item is really important to complete for its milestone, but it can be scoped out. Work: High It's not clear what the solution is. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

BenHenning commented Aug 2, 2019

It's important that a developer-only menu exist in the navigation drawer to provide a variety of debugging utilities. Currently needed functionality:

  • Profile functionality
    • Generate multiple child profiles at once with variations like profile with short name, profile with max characters, profile with pin, profile with image, etc.
    • Reset to admin profile only (deleting child profiles) & admin pin
  • Mark recently played (requires validation to make sure the app doesn't end in a broken state)
    • Topics
    • Stories
    • Chapters
  • Mark completed (requires validation to make sure the app doesn't end in a broken state)
    • Topics
    • Stories
    • Chapters
  • View logs
    • Analytics event logs
    • Logcat logs
    • View performance analytics (once available), and introduce option to reset these counters
  • Directly accessing learning material
    • Topics (requires topic ID)
    • Explorations (requires topic ID, story ID, and exploration ID)
    • Revision cards (requires topic ID & subtopic ID)
    • Concept cards (requires skill ID)
  • App-wide behavior changes
    • Force all hints/solutions on by default (toggle)
    • Fix question generation seed to a specific value (to have reproducible practice sessions)
    • Force app to run in wifi/cellular/no network case
    • Switching the Oppia backend (e.g. between production, testing, and local)
  • Miscellaneous (one-off actions)
    • Crash the app
    • Force restart the app
    • Dump all datastores to a shared file location to make it easy to pull off the device (e.g. for release version of Android)
    • Force admin authentication flow
@BenHenning BenHenning added Type: Improvement Priority: Important This work item is really important to complete for its milestone, but it can be scoped out. labels Aug 2, 2019
@BenHenning BenHenning added this to the Prototype milestone Aug 2, 2019
@BenHenning
Copy link
Member Author

This is blocked on #22 for the nav drawer, #16 for profile interaction, #5 for network endpoint selection, #12 for dumping the database, #18 for activity tracking logs, and #8 for viewing recent app logs. This is also blocked on #23, #24, #27, #40, #41, and #42 for direct jumping into Oppia activities.

Note that this work item can be built in multiple pieces when downstream work is completed and becomes available for debugging. Alternatively, this issue could instead track introducing the essential framework for adding debugging settings and feature-specific settings can be moved into the work items tracking the introductions of those features. Which approach is taken will be determined once this project is started.

@BenHenning BenHenning changed the title Developer menu Developer menu [Blocked: #5, #8, #12, #16, #18, #22, #23, #24, #27, #40, #41, #42] Aug 12, 2019
@BenHenning BenHenning changed the title Developer menu [Blocked: #5, #8, #12, #16, #18, #22, #23, #24, #27, #40, #41, #42] Developer menu [Blocked: #5, #8, #12, #16, #18, #22, #23, #24, #27, #40, #41, #42] Aug 12, 2019
@BenHenning BenHenning modified the milestones: Prototype -- UI, Minimal Viable Product Sep 17, 2019
@BenHenning BenHenning changed the title Developer menu [Blocked: #5, #8, #12, #16, #18, #22, #23, #24, #27, #40, #41, #42] Developer menu [Blocked: #8, #12, #16, #18, #22, #23, #24, #27, #40, #41, #42] Sep 17, 2019
@BenHenning BenHenning changed the title Developer menu [Blocked: #8, #12, #16, #18, #22, #23, #24, #27, #40, #41, #42] Developer menu [Blocked: #12, #16, #18, #22, #23, #24, #27, #40, #41, #42] Sep 17, 2019
@BenHenning BenHenning modified the milestones: Minimal Viable Product, Global Availability Jun 23, 2020
@BenHenning BenHenning changed the title Developer menu [Blocked: #12, #16, #18, #22, #23, #24, #27, #40, #41, #42] Developer options menu Feb 19, 2021
@BenHenning BenHenning added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). issue_type_enhancement Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Z-ibt Temporary label for Ben to keep track of issues he's triaged. labels Sep 16, 2022
@BenHenning BenHenning removed this from the Global Availability milestone Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Priority: Important This work item is really important to complete for its milestone, but it can be scoped out. Work: High It's not clear what the solution is. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Development

No branches or pull requests

3 participants