Request: Cross‑App Reminder/Task Syncing + Persistent Conversation State for Android Multitasking

Question

I’m a daily Copilot user on Android, and I’ve identified two technical limitations that significantly impact usability for anyone who multitasks or relies on Copilot for workflow support.

1. Cross‑App Syncing for Reminders, Tasks, and Calendar Events

Currently, Copilot can create reminders or calendar events only when explicitly instructed, and only within its own environment. There is no integration layer that syncs with:

• Android system reminders
• Android task managers
• third‑party task apps
• native calendar apps

Technical Impact

This creates friction for users who rely on natural‑language reminders during conversation. Without cross‑app syncing, reminders are lost unless manually transferred to another app.

Real‑Life Cognitive Load Impact

Many users (myself included) use Copilot during moments of high cognitive load — juggling school, work, home responsibilities, and daily planning. When Copilot helps me plan something, I often intend to add it to my task app or calendar, but the mental context switches so quickly that the reminder is lost unless I manually capture it immediately.

This isn’t forgetfulness; it’s the reality of managing multiple responsibilities at once.

Cross‑app syncing would reduce the pressure of having to remember every step of the process. Instead of:

• planning something with Copilot
• switching apps
• manually entering the task
• hoping I don’t get distracted mid‑switch

…the reminder would be captured automatically.

This would provide real relief for users who experience:

• high daily mental load
• frequent task switching
• executive function challenges
• busy schedules with many moving parts

Proposed Solution

Implement a cross‑app integration layer using:

• Android Intents
• Calendar Provider API
• Reminders/Tasks API hooks
• optional OAuth‑based connections for third‑party apps

This would allow Copilot to automatically write reminders or tasks to the user’s preferred system app without requiring manual switching.

2. Persistent Conversation State on Android (Background Process Stability)

When switching between Copilot and other apps (e.g., Microsoft Word), the Copilot thread frequently resets. This appears to be caused by Android’s background process management (Doze mode, memory pressure, or task eviction).

Technical Impact

This breaks conversational continuity and makes Copilot difficult to use for:

• writing
• research
• studying
• multitasking workflows

Proposed Solution

Implement one or more of the following:

• foreground service mode for active conversations
• state persistence using local storage snapshots
• conversation session caching
• improved lifecycle handling for onPause() / onStop() events
• optional “pinned conversation” mode to prevent eviction

This would allow Copilot to maintain context even when Android kills the background process.

Why These Features Matter

These improvements would significantly enhance Copilot’s reliability for users who depend on it for:

• academic work
• writing
• planning
• task management
• real‑time problem solving

Cross‑app syncing and persistent conversation state would make Copilot feel like a true assistant rather than an isolated app.

Thank you for reviewing this request. I believe these enhancements would benefit a large portion of the Android user base.

Answer 1

The described capabilities and implementation details for cross‑app reminder/task syncing and persistent conversation state on Android are not covered in the provided context.

---

References:

• Microsoft 365 Copilot release notes
• Deployment overview for the Microsoft 365 Copilot app
• Android word is so stripped back, its useless, will you be improving it soon, or do I have to go elsewhere for something worth using - Microsoft Q&A
• Start Task Button missing in Copilot - Microsoft Q&A
• Copilot Rewrite Feature not working in Classic Outlook - Microsoft Q&A
• Desktop icons I would like to remove. - Microsoft Q&A
• Is sql copilot free or is a commercial option - Microsoft Q&A