Hey there, sit back, relax, and enjoy the story about how namelss, an anonymous feedback platform was created all from scratch during the COVID pandemic.
Since my full-time job got converted to WFH setup, I was wondering what to with the extra time I am saving these days (ex: office commute time, no self-cooking time, etc).
Also, I wanted to learn Clojure and wanted to create a well-structured production-ready app.
So I started looking for a project idea to work on.
Just then I found one of my colleagues was struggling to find a tool wherein he can be the single host and invite other people to give feedback in real-time (sort of chatroom ) but all the participants can be anonymous or named based on their personal preferences.
Bang! This was a perfect idea and requirement intersection wherein I could have achieved all that I wanted (side project + Clojure based app).
Within no time I wrote an RFC/ADR doc around the concept.
As soon as I felt I have captured basic requirements from the project, I started work on it as well.
In just 2 months, working mostly on weekends and sometimes usual days, I could make it production-ready and here I am launching it today.
Product hunt page
(Please upvote on product hunt if you like the project)
About Namelss
🙅 No login/auth required by host or participants
🎭 Participants can be totally anonymous
✈️ Unlimited participants can join
📥 The host can export feedbacks/chats as CSV
🔒The host can lock room for entry when required participants have joined in.
⏳Realtime chatrooms and sessions
Bonus :
📱The app is a PWA so it can be installed on any device
🔐 Conversations are E2E encrypted
🕸️ Minimal UI
📟 Open Source
It helps with :
People giving feedback can be totally anonymous
The host can interact and introspect feedback with audience realtime
No limit on the number of people that can join the same room at a time
No context of the data being stored
More details in the Github repo here
Top comments (14)
Really cool. Do you think you could share, or maybe explain, how you wrote the RFC/ADR doc? I always have a hard time with that part of the process
EDIT: Should have checked first, here's the ADR docs.google.com/document/d/1Yhp8g4...
Hey Yes. Glad you found it. Let me know if i can help you with something else :D
Haha.. Glad you liked it x 10e100 times !
Nice, come and give feedback to dev.to
Done sir
Good job design looks nice and clean too.
How many concurrent connection the web socket will able to handle?
Haven't load tested it yet, since this was more of a MVP
I always wanted to know
how do we decide how many concurrent web sockets can be established?
Ideally you shouldn't have a limit on that. If you do so then you are just limiting your customers you to use your product.
Really awesome !! Would be interested to know where it is hosted. Or rather the deployment architecture if you will
Yes. The ADR doc has all the details. docs.google.com/document/d/1Yhp8g4...
TLDR : Frontend on netlify
Backend : GCP VM instance
You are havr installed pgSQL in VM or your by pgSQL instance from Google Cloud
Right now on VM, but working on to migrate data to cloudSQL