Content
View differences
Updated by Marc Alcobé 3 months ago
**As a** team member or field worker using OpenProject on **As** a tablet \[enter role of user\]
**I want** a dashboard-style Home screen optimized for landscape orientation want to** \[enter objective\]
**so that** I can quickly understand my current work, manage my time, and navigate to the right projects or work packages without unnecessary navigation \[enter desired result\]
**Acceptance criteria**
* When the app runs on a tablet-sized screen in landscape mode (using the breakpoint of 900px as reference), the Home screen displays a **two-column layout**.
* The Home screen uses the full horizontal space without empty or stretched areas.
* All widgets used in mobile mode can also be used in the tablet mode:
* Showing live, up-to-date data
* Can be interacted with (open work packages, projects, or timers)
* Scrolls independently if its content exceeds the available space
* The global search bar is visible at the top of the Home screen.
* The bottom navigation bar on mobile is now translated to a persistent side navigation bar always visible on the top navigation modules.
* A centred configuration bottom sheet allows users to:
* Enable or disable individual widgets
* Assign widgets to the left or right column of the layout
* Widget visibility and placement are persisted per user. <br>
**Technical notes**
* The tablet Home layout is enabled when the viewport width meets the tablet **breakpoint: 900px**.
* In portrait orientation on small tablets, the phone Home layout is shown instead.
* Widgets are rendered as independent, reusable components.
* Widget configuration is stored per user and synced across sessions and logins.
* Data is fetched in parallel to avoid blocking the Home screen. The same loading implementation as in mobile is used <br>
**Permissions and visibility considerations**
* If the user lacks permission to view any of the modules should _To whom is this feature visible?_
* _When is it not see the respective widgets on the Home page. visible?_
**Translation considerations**
* 3 new strings are added on the bottom sheet _Key terms and phrases in comparison the mobile mode to be translated:
* Left column
* Right column
* Inactive
key languages_
**Out of scope**
* Portrait-optimized tablet layout
* Drag-and-drop reordering <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of widgets
* Custom dashboards beyond the provided widgets
* Desktop-specific Home behavior changes._
**I want** a dashboard-style Home screen optimized for landscape orientation
**so that** I can quickly understand my current work, manage my time, and navigate to the right projects or work packages without unnecessary navigation
**Acceptance criteria**
* When the app runs on a tablet-sized screen in landscape mode (using the breakpoint of 900px as reference), the Home screen displays a **two-column layout**.
* The Home screen uses the full horizontal space without empty or stretched areas.
* All widgets used in mobile mode can also be used in the tablet mode:
* Showing live, up-to-date data
* Can be interacted with (open work packages, projects, or timers)
* Scrolls independently if its content exceeds the available space
* The global search bar is visible at the top of the Home screen.
* The bottom navigation bar on mobile is now translated to a persistent side navigation bar always visible on the top navigation modules.
* A centred configuration bottom sheet allows users to:
* Enable or disable individual widgets
* Assign widgets to the left or right column of the layout
* Widget visibility and placement are persisted per user.
**Technical notes**
* The tablet Home layout is enabled when the viewport width meets the tablet **breakpoint: 900px**.
* In portrait orientation on small tablets, the phone Home layout is shown instead.
* Widgets are rendered as independent, reusable components.
* Widget configuration is stored per user and synced across sessions and logins.
* Data is fetched in parallel to avoid blocking the Home screen. The same loading implementation as in mobile is used
**Permissions and visibility considerations**
* If the user lacks permission to view any of the modules should
* _When is it
**Translation considerations**
* 3 new strings are added on the bottom sheet
* Left column
* Right column
* Inactive
* Portrait-optimized tablet layout
* Drag-and-drop reordering
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed
* Custom dashboards beyond the provided widgets
* Desktop-specific Home behavior