Description:
Currently, if a user starts typing a message in one conversation and then switches to another to copy or reference some content, the partially written text in the original conversation is lost. This can be frustrating, especially when drafting complex queries or responses, as users have to rewrite their message from scratch.
I propose adding a “Draft” functionality to prevent this issue. Here’s how it could work:
Key Features:
- Automatic Draft Saving: Any partially written text in a conversation is automatically saved and restored when the user returns to that conversation.
- Visual Indicator: Conversations with unsent drafts are marked with a visual indicator (e.g., a red “!” or a “Draft” label) in the conversation list.
- Cross-Session Continuity: Drafts remain intact even if the user logs out or closes the browser, allowing them to pick up where they left off later.
Benefits:
Improved User Experience: Users can seamlessly switch between conversations without worrying about losing their progress.
Time-Saving: Eliminates the need to rewrite unfinished messages.
Error Prevention: Reduces the frustration caused by accidental text loss.
Implementation Suggestions:
Local Storage: Use browser-based local storage to save drafts temporarily for quick restoration.
Cloud Sync: Optionally, save drafts to the server to allow synchronization across devices.
This functionality would align with similar features in other platforms like Gmail or WhatsApp, where “Draft” messages significantly enhance user experience.