microsoft / microsoft/azurechat
Chat start buttons UX does not differentiate blank from extension conversations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
Based on user feedback of the solution users do not differentiate the following buttons in the home page, indicating their differences are not explicit enough in the UI:
- New chat button found in the top-hand of the conversations history (src/features/chat-page/chat-menu/new-chat.tsx)
- Start chat button at the bottom of extension cards (src\features\extensions-page\extension-card\start-new-extension-chat.tsx)
As both buttons may appear together in the homepage, the final user may not catch that one starts a conversation with no extension while the other triggers the extension in new conversation
What we would recommend are the following possibilities:
- Remove the history "New chat" button and include a blank default template into the extensions list, making the extension panel the only way to start a conversation
- Change the naming and color accentuation of buttons to clearly distinguish one from another
- Add a description to the extension list to signify it's usage and distinguish it from the history new chat button
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing src/features/chat-page/chat-menu/new-chat.tsx with src/features/extensions-page/extension-card/start-new-extension-chat.tsx and inspect how both appear on the homepage. The issue lists several possible UX directions but does not choose one or define acceptance criteria, so the intended distinction and completion condition need maintainer clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100