Content
View differences
Updated by Marc Alcobé 3 months ago
### **1\. Device detection & layout switching**
* The app detects tablet-class screen sizes (e.g., iPad, Android tablets, foldables in large mode)
* Tablet devices receive a **dedicated layout**, not the phone layout scaled up
* The UI adapts when switching between:
* Portrait and landscape
* Split-screen / multi-window modes (where supported)
* Until there is a specific user interface designed for small tablets and portrait modes, the breakpoint used to switch between phone and tablet UI will be 900px
### **2\. Optimized use of screen real estate**
* Tablet layouts:
* Use multi-column or split-pane views where appropriate
* Avoid large empty areas or oversized single-column lists
* Key screens (e.g., project list, work packages, time tracking...) display:
* More items on screen
* More contextual information without additional taps
### **3\. Tablet-friendly navigation**
* Navigation allows:
* Persistent sidebars or panels where appropriate
* Faster switching between projects, modules, and views
* Users can move between:
* Lists and details
* Projects and work packages
* with fewer taps than on phone layouts
### **4\. Workflows are supported**
* Users can:
* Browse and edit work packages while keeping context visible
* Switch between related items without losing their place
* The UI supports:
* Touch
* Hardware keyboard (where available)
### **5\. Consistency with OpenProject**
* Tablet UI follows:
* OpenProject design style
* Terminology
* Visual identity
* Core workflows remain recognizable across:
* Desktop
* Phone
* Tablet
### **6\. Foundation for multi-device strategy**
* Tablet UI architecture:
* Can be extended to larger devices (e.g., foldables, future desktop-class mobile)
* Does not block future device-specific layouts
* No hard-coded phone-only assumptions remain in core layout logic
* The app detects tablet-class screen sizes (e.g., iPad, Android tablets, foldables in large mode)
* Tablet devices receive a **dedicated layout**, not the phone layout scaled up
* The UI adapts when switching between:
* Portrait and landscape
* Split-screen / multi-window modes (where supported)
* Until there is a specific user interface designed for small tablets and portrait modes, the breakpoint used to switch between phone and tablet UI will be 900px
### **2\. Optimized use of screen real estate**
* Tablet layouts:
* Use multi-column or split-pane views where appropriate
* Avoid large empty areas or oversized single-column lists
* Key screens (e.g., project list, work packages, time tracking...) display:
* More items on screen
* More contextual information without additional taps
### **3\. Tablet-friendly navigation**
* Navigation allows:
* Persistent sidebars or panels where appropriate
* Faster switching between projects, modules, and views
* Users can move between:
* Lists and details
* Projects and work packages
* with fewer taps than on phone layouts
### **4\. Workflows are supported**
* Users can:
* Browse and edit work packages while keeping context visible
* Switch between related items without losing their place
* The UI supports:
* Touch
* Hardware keyboard (where available)
### **5\. Consistency with OpenProject**
* Tablet UI follows:
* OpenProject design style
* Terminology
* Visual identity
* Core workflows remain recognizable across:
* Desktop
* Phone
* Tablet
### **6\. Foundation for multi-device strategy**
* Tablet UI architecture:
* Can be extended to larger devices (e.g., foldables, future desktop-class mobile)
* Does not block future device-specific layouts
* No hard-coded phone-only assumptions remain in core layout logic