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

Landscape layouts #56

Open
BenHenning opened this issue Aug 2, 2019 · 3 comments
Open

Landscape layouts #56

BenHenning opened this issue Aug 2, 2019 · 3 comments
Labels
enhancement End user-perceivable enhancements. Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Priority: Nice-to-have This work item is nice to have for its milestone. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

Many users prefer to use landscape mode in apps, and Oppia's player view has good potential to better leverage landscape (e.g. having the content & interactions side-by-side rather than top-on-bottom). Although not a specific necessity for the prototype, supporting landscape layouts would go a long way toward demonstrating a well-rounded and polished user experience.

If this is not completed for the prototype, the app should instead be frozen in portrait mode until proper landscape support can be added.

@BenHenning BenHenning added Type: Improvement Priority: Nice-to-have This work item is nice to have for its milestone. labels Aug 2, 2019
@BenHenning BenHenning added this to the Prototype milestone Aug 2, 2019
@BenHenning
Copy link
Member Author

BenHenning commented Aug 2, 2019

Since this affects all screens in the app, it's potentially blocked by #51, #52, #53, #54, #55, #48, #46, #44, #42, #41, #40, #27, #28, #29, #30, #31, #32, #33, #34, #35, #26, #25, #24, #23, and #22. There may be future UI work that require landscape layouts work not linked here, and not all of the above layouts will require landscape-specific work. This can also be done during the development of those features, and in multiple pieces in order to optimize the landscape experience for users.

@BenHenning BenHenning changed the title Landscape layouts Landscape layouts [Blocked: #22, #23, #24, #25, #26, #27, #28, #29, #30, #31, #32, #33, #34, #35, #40, #41, #42, #44, #46, #48, #51, #52, #53, #54, #55] Aug 12, 2019
@BenHenning BenHenning modified the milestones: Prototype -- UI, Minimal Viable Product Sep 17, 2019
@BenHenning BenHenning changed the title Landscape layouts [Blocked: #22, #23, #24, #25, #26, #27, #28, #29, #30, #31, #32, #33, #34, #35, #40, #41, #42, #44, #46, #48, #51, #52, #53, #54, #55] Landscape layouts [Blocked: #22, #23, #24, #26, #27, #28, #29, #30, #31, #32, #33, #34, #35, #40, #41, #42, #44, #46, #48, #51, #52, #53, #54, #55] Sep 17, 2019
@rt4914 rt4914 changed the title Landscape layouts [Blocked: #22, #23, #24, #26, #27, #28, #29, #30, #31, #32, #33, #34, #35, #40, #41, #42, #44, #46, #48, #51, #52, #53, #54, #55] Landscape layouts Apr 13, 2020
@BenHenning BenHenning modified the milestones: Minimal Viable Product, Global Availability, Beta Jun 23, 2020
@anandwana001
Copy link
Contributor

@rt4914 After the last gsoc, I think we had covered almost everything for landscape view.
Can we close this issue?

@rt4914
Copy link
Contributor

rt4914 commented Apr 19, 2021

@anandwana001 Actually that project covered some of the major screen but not all. As per this document there are multiple screens which are pending.

@Broppia Broppia added issue_type_infrastructure Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 14, 2022
@BenHenning BenHenning added issue_type_enhancement Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. 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. and removed issue_type_infrastructure Impact: Low Low perceived user impact (e.g. edge cases). labels Sep 15, 2022
@BenHenning BenHenning removed this from the Beta milestone Sep 16, 2022
@seanlip seanlip added enhancement End user-perceivable enhancements. and removed issue_user_learner labels Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement End user-perceivable enhancements. Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Priority: Nice-to-have This work item is nice to have for its milestone. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Development

No branches or pull requests

5 participants