1.8 KiB
1.8 KiB
AeThex Connect – Progress & Next Steps
Current Progress
1. UI & Frontend
- Modern, branded landing and login pages (Astro + React + Tailwind)
- Glassy, Discord-style chat/voice UI with channel, member, and chat areas
- Demo login and account linking UI (AeThex + Matrix, now being phased out)
- WebRTC integration for voice (UI and hooks scaffolded)
2. Matrix Integration (Deprecated)
- MatrixProvider and context for chat/voice (now being removed due to auth/friction)
- Demo login attempted with Matrix test accounts (blocked by Matrix.org restrictions)
- Error handling and feedback for Matrix login failures
3. Architecture Decisions
- Decided to move away from Matrix for chat/auth due to complexity and lack of control
- Plan to use AeThex-native authentication and backend for chat/voice
- WebRTC will be used for voice, with custom signaling
Next Steps
1. Backend
- Scaffold a Node.js (or similar) backend for:
- AeThex account authentication (JWT/session)
- Real-time chat (Socket.io or websockets)
- WebRTC signaling for voice
- Add basic chat channels, DMs, and presence
2. Frontend
- Remove Matrix login and context from UI
- Connect chat/voice UI to new backend (Socket.io/websockets for chat, WebRTC for voice)
- Use AeThex login for all authentication
- Add error handling, loading states, and user feedback
3. Features & Polish
- Add moderation tools, premium features, and integrations as needed
- Polish UI/UX for onboarding, chat, and voice
- Prepare for MVP launch and user testing
Summary:
- UI and core experience are in place
- Matrix is being replaced with a custom AeThex-native backend
- Next: Build backend, connect frontend, and iterate on features
This README reflects the current state and roadmap for AeThex Connect as of January 2026.