Content
View differences
Updated by Marc Alcobé 13 days ago
* **Mobile parity with the web app:** Today, key meeting workflows are primarily web-first. Users working away from a desk need comparable access to meeting information and updates without switching to a browser or postponing tasks.
* **Support real project execution in the field:** Meetings are often where decisions, next steps, and ownership get captured. Enabling meeting creation and editing on mobile helps teams document outcomes immediately—especially during on-site work, travel, or customer-facing sessions.
* **Reduce workflow fragmentation:** Without mobile support, users rely on ad-hoc notes or external tools and later re-enter information into OpenProject, increasing duplication, missed details, and inconsistency.
* **Ensure consistent governance and access control:** Bringing meetings to mobile must preserve OpenProject’s existing permission model and visibility rules so that sensitive project information remains appropriately restricted across devices.
* **Foundation for future improvements:** A robust mobile meetings baseline (list/view/create/edit with safe content handling) establishes the technical and UX groundwork for later enhancements (e.g., richer editing, tighter linking to work packages, improved performance/caching) without rethinking the entire feature end-to-end.
* **Support real project execution in the field:** Meetings are often where decisions, next steps, and ownership get captured. Enabling meeting creation and editing on mobile helps teams document outcomes immediately—especially during on-site work, travel, or customer-facing sessions.
* **Reduce workflow fragmentation:** Without mobile support, users rely on ad-hoc notes or external tools and later re-enter information into OpenProject, increasing duplication, missed details, and inconsistency.
* **Ensure consistent governance and access control:** Bringing meetings to mobile must preserve OpenProject’s existing permission model and visibility rules so that sensitive project information remains appropriately restricted across devices.
* **Foundation for future improvements:** A robust mobile meetings baseline (list/view/create/edit with safe content handling) establishes the technical and UX groundwork for later enhancements (e.g., richer editing, tighter linking to work packages, improved performance/caching) without rethinking the entire feature end-to-end.