How lalit2107/smart-email-assistant works
Project type and purpose
• This is a full-stack AI-powered email assistant that combines:
• A Chrome Extension (email-writer-ext) to inject UI into webmail
• A React frontend (email-writer-react) for tone selection and editing
• A Spring Boot backend (email-writer-sb) that proxies requests to the Gemini API
• Purpose: let end users generate professional/friendly/casual emails via a local Chrome Extension UI, using Google’s Gemini API for AI content generation.
File structure
• Top-level folders:
• email-writer-ext: Chrome extension manifest, content script, CSS
• email-writer-react: React SPA (public, src, package.json, Vite config)
• email-writer-sb: Spring Boot service (pom.xml, src/main/java, controller, service, request DTO)
• Patterns & tools:
• Frontend: React + Vite
• Backend: Spring Boot MVC (EmailGeneratorController → EmailGeneratorService → Gemini API)
• Extension: content.js injected into pages, communicates with React UI or directly with backend
• Deployment/config:
• manifest.json defines extension permissions & entry points
• application.properties holds backend configs
• package.json / pom.xml drive builds
README for additional insights
• Confirms architecture: React frontend, Spring Boot backend, local Chrome Extension, Gemini API as external service
• Features: tone selection, AI-generated content, local execution with potential cloud extension
a. Main components
1. Chrome Extension
• content.js / content.css running in user’s browser context
• UI trigger (button or popup)
2. React Frontend
• Tone selection UI (hosted locally or served as extension popup iframe)
3. Spring Boot Backend
• REST API endpoints (/generate-email)
• Authentication & request forwarding
4. Gemini API (External Service)
• AI model endpoint
b. Relationships & interactions
• User opens email composer → Extension content script injects “Generate AI Draft” button
• On click, Extension loads React UI
• React UI issues HTTP POST to Spring Boot (/api/email)
• Spring Boot Service builds request → calls Gemini API → receives generated text
• Spring Boot returns AI-generated email to React UI → UI displays in extension overlay → user inserts content
c. Architectural patterns/design principles
• Separation of concerns: Extension vs. UI vs. Business Logic
• MVC in backend: Controller → Service → External API
• SPA pattern in React for dynamic UI
• Loose coupling: backend only knows external API, frontend only knows backend API
d. Key technologies/frameworks
• Chrome Extension APIs (manifest v3, content scripts)
• React + Vite (SPA bundling)
• Spring Boot (REST controllers, dependency injection)
• Gemini API (AI service)