[PHASE 7] Web UI Technology Decision — Angular vs Alternatives

[sujankim]

🌐 Phase 7 — Web UI Technology Decision

Hello everyone! 👋

Phase 6 (Agent System) is now complete. We are ready to start
planning Phase 7 — the Web UI for Jarvis AI Platform.

Before we write any code, we need to decide on the technology
stack. This is an important decision that will affect everyone
who contributes to the frontend.

---

🎯 What the Web UI Needs to Do

The Web UI must support:

• Real-time streaming chat (Server-Sent Events)
• Session management (list, switch, create sessions)
• Memory management (view, add, delete memories)
• Document upload (RAG file management)
• Agent dashboard (start tasks, see ReACT steps live)
• Voice interface (record audio, play responses)
• Settings panel (configure voice, providers)
• Authentication (JWT login/logout)

---

🤔 The Question

Which frontend framework should Jarvis AI Platform use?

---

🅰️ Option A — Angular

Pros:

• Maintainer (Sujan) knows Angular well
• Full-featured framework (routing, forms, HTTP built-in)
• TypeScript by default — strong type safety
• Angular Material = beautiful components out of the box
• Enterprise-grade, excellent for large apps
• Great CLI (ng generate)
• Two-way data binding for forms

Cons:

• Steeper learning curve for new contributors
• More boilerplate compared to React/Vue
• Heavier bundle size
• Slower initial setup

Tech stack:

• Angular 18+ with Angular Material
• TypeScript
• RxJS for reactive streams (pairs naturally with WebFlux SSE)
• Angular CLI

---

⚛️ Option B — React

Pros:

• Most popular frontend framework worldwide
• Largest contributor pool (most devs know React)
• Flexible — choose your own libraries
• Lighter than Angular
• Huge ecosystem (Shadcn UI, Tailwind, etc.)

Cons:

• Not opinionated — need to choose routing, state, forms separately
• Maintainer would need to learn React patterns
• JavaScript by default (TypeScript optional)

Tech stack:

• React 18+ with TypeScript
• Vite (build tool)
• React Router
• TanStack Query (data fetching)
• Shadcn UI or Tailwind CSS

---

🟢 Option C — Vue.js

Pros:

• Gentler learning curve than Angular/React
• Clean syntax — easy to read
• Good for contributors new to frontend
• Nuxt.js available for SSR

Cons:

• Smaller contributor pool than React
• Less opinionated than Angular
• Maintainer would need to learn Vue

Tech stack:

• Vue 3 with TypeScript
• Vite
• Vue Router
• Pinia (state management)
• Vuetify or PrimeVue components

---

🔷 Option D — Next.js (React-based)

Pros:

• React ecosystem + built-in routing
• SSR support (better SEO)
• File-based routing (simple to learn)
• Vercel deployment friendly

Cons:

• Adds SSR complexity we may not need
• Maintainer would need to learn Next.js

---

💭 Maintainer's Thoughts

I currently know Angular best. However, I want to choose
what is best for the project and contributors long-term,
not just what is easiest for me personally.

Key considerations:

1. Contributor friendliness — more contributors = better project
2. Type safety — TypeScript preferred for a large codebase
3. SSE streaming support — must handle AI token streams well
4. Component library — need good pre-built UI components
5. Maintainability — must be easy to maintain long-term

---

📊 Quick Comparison

Feature	Angular	React	Vue	Next.js
Learning curve	High	Medium	Low	Medium
TypeScript	Built-in	Optional	Optional	Optional
Contributor pool	Medium	Large	Medium	Large
Bundle size	Large	Medium	Small	Medium
SSE support	✅	✅	✅	✅
Component library	Angular Material	Shadcn/MUI	Vuetify	Shadcn
Maintainer familiarity	⭐⭐⭐	⭐	⭐	⭐

---

🗳️ Please Vote and Share Your Opinion!

React to this post with:

• 👍 = Use Angular
• ❤️ = Use React
• 🚀 = Use Vue
• 👀 = Use Next.js
• 😕 = Something else (comment below)

Please also comment with:

1. Which option you prefer and WHY
2. Your experience level with each framework
3. Any concerns or suggestions

---

⏰ Decision Timeline

We will make a final decision in 2 weeks (by July 14, 2026).

After the decision:

• Create Phase 7 tracking issue
• Set up frontend project structure
• Create contributor issues for UI components

---

📚 Background Reading

• Jarvis AI Platform GitHub
• ROADMAP.md
• Spring Boot 4 + WebFlux backend

All contributors and community members are welcome to vote!
The backend is Java/Spring Boot — frontend can be any framework.

cc @all-contributors

---

This discussion will be pinned until a decision is made.