[Design] Rethinking Duo for the IDE
Description
Concept exploration intended to spark discussion around a Duo Chat experience that's better integrated with the IDE. Broken up into four segments:
Goal is to gather feedback and get alignment before breaking up into iterable implementation issues starting with VS Code before expanding to other IDEs.
Quick prototype example prototype_IDENative_DuoChat
JTBD
Job performer | Code author |
---|---|
Main job | Develop improvements for my application (e.g., performance, reliability, security, user experience) |
Target outcomes | Minimize the chances of mistakes or missed configuration steps that delay access to resources or services, Minimize the time it takes to write or refactor code to meet the required functionality or performance standards, Minimize the likelihood that code refactoring introduces new bugs or breaks existing functionality |
Methods | Adopt recognizable patterns, consolidate features into single access point, provide shortcuts for common actions |
Definitions
- IDE First:
- Provide a Duo experience that is purpose built for developer workflows inside the IDE instead of repurposing an experience that's intended for different jobs/job performers in a different environment.
- It does NOT mean that we must use IDE-specific components to build Duo.
Useful links
Edited by Taylor Vanderhelm