DDovel Team
CockpitOverview & what needs youChatAsk the Product agentFigma SyncLive diff vs the PRDFeaturesEvery feature & its specFlowsAI-inferred from the designs✓BacklogWhat's left to buildScreensPages, specs & criteriaRoadmapNew in Figma → proposalsDriftWhat changed in designMeetingsCalls → decisions → PRDTeamPeople + their AI support
Figma Dovel iQ v0.3 MVP (Active) · 2026-10-10
Dovel Team
PProduct agentsupports Design & PM✓BBackend agentsupports EchecomingFFrontend agentsupports the FE buildcomingQQA agentsupports QualitycomingOOrchestrator agentsupports Opscoming
Flows / Notification Preferences / notification

notification

notification · Figma 7192:64558

notification
Scopednot in the frontend yetFigma 7192:64558

Frontend

No matching Flutter page yet — not built.

Endpoints this screen calls · 2 endpoints, 0 confirmed in code · the Backend agent owns these

GET /settings/notification-preferencesPUT /settings/notification-preferences

Acceptance criteria · drafted by Product agent

  • User can view their current notification preferences for product, payment, and marketing alerts, loaded via GET /settings/notification-preferences on screen entry.
  • User can toggle each notification category (product, payment, marketing) independently and see the change reflected immediately in the UI.
  • On save, the app calls PUT /settings/notification-preferences with the updated preference set and shows a success confirmation (e.g., 'Preferences saved') on a 2xx response.
  • System displays an error message and preserves the user's unsaved selections if the GET or PUT call fails, allowing retry without losing changes.

What's on the screen

—
P
Product agent
supports Design & PM
×