Concord

Concord logo
User settings and themes page
Voice and message channel view

Inspiration

Initially one our teammates always had the idea of coming up with a privacy first messaging client two years ago. Questioning why can't we have a messaging client that's not observed by some private organization. With that idea we came up with the idea of making a similar messaging service client like Discord or Slack but communities can host their own servers with better privacy.

What it does

Concord allows users to communicate through voice and text channels that are secured through multiple layers of practices. Users can create and host instances of Concord and invite users into separate channels.

How we built it

Frontend: React, TypeScript & Tailwind CSS for a native desktop feel that's similar to discord for familarity. Zustand for session management, cookies, local storage.

Backend: Hono for API Frameworks, Bun for runtime, Prisma for database management, Zod for runtime validation, Socketio and WebRTC for message/voice, Scaler for database migrations, OpenAPI for documentation

EngineX for deployment

Challenges we ran into

Paul: I initially had a hard time adapting to the learning curve with the backend tech stack, then implementing Socketio events took a fair amount of time.

Accomplishments that we're proud of

Paul: Fully implementing real time events after some period of absence while collaborating with a frontend engineer to integrate a live messaging system was alot of fun. Experimenting with other tech stacks other than express/node in the JS/TS ecosystem has been extremely eye opening and fun, will continue to explore it.