Content
View differences
Updated by Marc Alcobé 13 days ago
Implementing new meeting functionality that does not exist in the web browser app baseline (e.g., brand-new meeting concepts, new workflows, or new permission models).
* Redesigning the meeting data model on the backend beyond what is required for mobile parity.
* Adding advanced editor features beyond what is needed for safe round-trip fidelity with existing meeting content.
* Building integrations outside the mobile app (e.g., calendar sync, email invitations, external conferencing integrations) unless already part of the web baseline and explicitly required for parity.
* Creating a full offline-first experience with queued writes/sync; the initial scope only requires graceful handling of offline/failed saves (no background synchronization).
* Admin/workspace configuration changes related to meetings (settings, global policies) unless they are required for mobile parity and already supported on web.
* Redesigning the meeting data model on the backend beyond what is required for mobile parity.
* Adding advanced editor features beyond what is needed for safe round-trip fidelity with existing meeting content.
* Building integrations outside the mobile app (e.g., calendar sync, email invitations, external conferencing integrations) unless already part of the web baseline and explicitly required for parity.
* Creating a full offline-first experience with queued writes/sync; the initial scope only requires graceful handling of offline/failed saves (no background synchronization).
* Admin/workspace configuration changes related to meetings (settings, global policies) unless they are required for mobile parity and already supported on web.