Hide Info tab #4447
Assignees
Labels
Impact: Low
Low perceived user impact (e.g. edge cases).
Issue: Needs Clarification
Indicates that an issue needs more detail in order to be able to be acted upon.
Z-ibt
Temporary label for Ben to keep track of issues he's triaged.
Comments
|
@JishnuGoyal can u assign me this task? i have solution for this task. |
|
@MihirShirgaonkar sorry this is actually being worked on by @JishnuGoyal as part of a broader project (he just wasn't able to self-assign before). |
Broppia
added
issue_type_infrastructure
Impact: Low
BenHenning
added
issue_type_bug
Z-ibt
BenHenning
pushed a commit
that referenced
this issue
Sep 27, 2022
* add EnableExtraTopicTabsUi platform parameter * use platform parameter to hide extra topic tabs * fix errors * shorten line length * add force method * make changes to the test. Not completed yet. * reset to develop * add tests * update to correct logic * change parameter name * fix some incorrect code * fix some incorrect code * adjust code changes for tests in this file * remove unused resources * lint * add platform parameter module to alpha kenya app component * remove unused resource - position with three tabs * nit: concise kdoc * add accidentally removed modules * update logic ; review required * lint * reset all changes to AlphaKenyaApplicationComponent.kt * add parameter to alpha kenya module * remove "isSuccessful" * add suggested changes * lint * update logic * update test logic to account for the removed tabs * lint * suggested changes * lint * partial: delete practice tab module * complete: remove practice tab module and enablePracticeTab * update logic * fix code after a bad merge * update some tests according to changes introduced due to hiding tabs * lint * update test due to hiding some tabs * lint * update tests * update rest of the tests to include changes from hiding tabs + modify chapter list PR * lint * dont use delegates * remove duplicate entry and revert the "reversion" * lint * remove unused resource * mend incorrect legacy logic * remove usages of delegates * lint * lint
BenHenning
added a commit
that referenced
this issue
Nov 22, 2022
…nctionality (#4699) <!-- READ ME FIRST: Please fill in the explanation section below and check off every point from the Essential Checklist! --> ## Explanation <!-- - Explain what your PR does. If this PR fixes an existing bug, please include - "Fixes #bugnum:" in the explanation so that GitHub can auto-close the issue - when this PR is merged. --> fixes #4452 fixes #4453 fixes #4454 fixes #4455 fixes #4456 fixes #4457 fixes #4458 fixes #4459 This PR introduces the SpotlightFragment into the codebase, which is essentially a powerful, robust API that can highlight or 'spotlight' certain parts of the UI to create an onboarding experience for the same. We introduce the [Spotlight library](https://github.com/TakuSemba/Spotlight) into the codebase handles the highlighting of certain elements on screen. The work done in this PR augments the functionality of the library, by dynamically adding arrows and hints which create an over-all Spotlight onboarding experience to the app, beautifully surfacing some functionalities of the app to a new user. We also work on making sure that the spotlight is only shown to a user only once - the protocol buffers are used to save which spotlight has already been seen. The purpose of this PR is to introduce an API that the future contributors can use to seamlessly integrate spotlights onto UI elements as and when needed, with minimal coding. This PR also implements spotlights for the onboarding, home, topic and exploration screens that are required at this time. For accessibility, the content descriptions of all the elements on which spotlights are required today are updated. If talkback is turned on, the spotlights will not show up. The entire spotlight functionality is also gated behind a feature flag. This entire PR is backed by tests. ## Essential Checklist <!-- Please tick the relevant boxes by putting an "x" in them. --> - [x] The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".) - [x] Any changes to [scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets) files have their rationale included in the PR explanation. - [x] The PR follows the [style guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide). - [x] The PR does not contain any unnecessary code changes from Android Studio ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)). - [x] The PR is made from a branch that's **not** called "develop" and is up-to-date with "develop". - [x] The PR is **assigned** to the appropriate reviewers ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)). ## For UI-specific PRs only <!-- Delete these section if this PR does not include UI-related changes. --> If your PR includes UI-related changes, then: - Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes - For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see [RTL guide](https://github.com/oppia/oppia-android/wiki/RTL-Guidelines)) - Add a video showing the full UX flow with a screen reader enabled (see [accessibility guide](https://github.com/oppia/oppia-android/wiki/Accessibility-(A11y)-Guide)) - Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing Co-authored-by: Ben Henning <[email protected]> Co-authored-by: madhurgera2 <[email protected]> Co-authored-by: JishnuGoyal <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
According to the recent user studies, the info tab does not provide much information to the user. Some users do not understand what to do on this screen and keep on clicking on the 'topic downloaded' button hoping to start a lesson.
Describe the solution you'd like
Remove the info tab and make the lessons tab as the default landing page for topics screen.
The text was updated successfully, but these errors were encountered: