IDE Extension vs. Web Application #26
sunilkhedar
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Introduction
To build a robust user interface for Sirji there can be multiple routes. The two main routes that we would like to brainstorm here are:
Key Insight: The design philosophy behind Sirji emphasizes the use of modular components for the messaging protocol, agents, tools, etc. These modular components will allow us to support multiple user interfaces.
Let's dive deeper into the characteristics, advantages, and disadvantages of each user interface option mentioned:
IDE extension:
Characteristics: This involves creating an extension that integrates directly into an IDE (like Visual Studio Code). The extension aims to enhance the user experience by providing direct access to Sirji's functionalities within the development environment.
Pros:
Cons:
Persona: An IDE extension is more suitable for a developer.
Web Application
Characteristics: This approach involves creating a stand-alone web application, similar to Devin, to be accessed through a web browser.
Pros:
Cons:
Persona: A web application is more suitable for individuals not specialized in software development.
Each user interface offers unique benefits & challenges and is suitable for different personas. We think that both interfaces are required to serve different user personas.
Our current plan is to first work on the IDE extension and then build a web solution.
But keeping this discussion open to hear your input.
Beta Was this translation helpful? Give feedback.
All reactions