I was building a social media platform for users to raise their voices. I have made a special algorithm for them, and it works really well.
I got ...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks broooooooooooo!!!!!
you implemented feedbacks so quick
and yeah now I'm in guilt that you've to remove your hard worked features but I think now it is more minimal and better UIX
I guess?
bro with profile icon make that profile to down side and a little bit big
small touch, but small bricks made house perfect.
can it be like this 👆
Yes...
Good Idea...
Ill make this!
thanks, this is what looks like when akhouri systems Founder & CEO enters the chat... 😂
✔🤣
people how you are expert in UIX
My reply Le: akhouri-anmol-kumar.github.io/APIC...
by the way please do not reply peak marketing 😂
Killing Widewave was the right move, and the hardest part of it — you already named it yourself: a feature users can't explain back in one sentence is one they won't miss. Every button you remove is also one fewer thing a new user has to learn, so minimalism compounds. Looking forward to seeing what the dashboard feels like now that it's calmer.
Thank you! 🙌 Today's devlog is coming soon. I've made some new changes, and now I'm working on refining the UI to make it feel even cleaner and smoother. Excited to share the updates!
Looking forward to today's devlog! If you can, share a before/after of the UI refinements — those screenshots always make the cleanup work click for readers.
i was just writing the todays devlog!
ill try add before and after too!
I’m learning the same lesson from a much smaller product.
Once something is live, adding another feature always feels productive, but sometimes the real bottleneck has nothing to do with the product anymore.
In my case I’ve basically stopped building for a bit because distribution is the bigger problem now.
Cutting something you already spent time building is probably harder than deciding not to build it in the first place 😅
So true! 😅 It's hard to let go of something you've already spent time building, but sometimes it's the right decision for the product. I think building and distribution both need their time, and knowing when to focus on which one is important. Thanks for sharing your experience!
Exactly. I’m starting to see distribution as part of the product itself rather than something you think about after launch. Out of curiosity, what are you focusing on most for Crowdwide right now product improvements or getting more people to discover it?
Honestly, both!!
I'm still improving Crowdwide's UI and core features, but I'm also trying to get more people to discover it and share their feedback. I want to make sure the platform is actually useful before focusing too much on growth.
The main thing I'm focusing on is giving new voices and smaller communities a better chance to get discovered. That's what I want Crowdwide to be different for!!
That makes sense. I like the idea of improving the product while already exposing it to real users instead of waiting for everything to feel “finished”. I’m experimenting with something similar right now, especially through content and community discussions.
Have you found any channel that’s bringing you better feedback so far — DEV, Reddit, direct outreach, or something else?
Honestly, DEV has been pretty helpful so far!! People here share genuinely useful suggestions, and I'm trying to implement the ones that make sense for Crowdwide.
I'm still exploring other channels too, but for now, DEV has been one of the best places for getting feedback and connecting with developers!!
Stripping CSS is the easy part; true minimalism is shaving DOM reflows off the client and keeping your pub/sub fan-out from incinerating connection pools the second those voices actually hit production.
Absolutely! UI minimalism is just one part of the process. The real challenge is making sure Crowdwide stays responsive and scalable when real users start interacting with it. That’s something I’ll keep focusing on as development progresses.
Minimal UI is strongest when it removes decisions rather than merely removing pixels. A useful next check is to pick the core task — posting, discovering, or raising an issue — and measure how many choices, taps, and ambiguities remain from entry to completion.
That's actually a really good way to look at it!! 👀 I was mostly focusing on making the UI look cleaner, but removing unnecessary decisions matters even more.
I'll try checking the core tasks this way and see where I can make things simpler for users. Thanks for the suggestion!!
nice cut on Widewave, removing the thing you spent the most time on is the hardest call. on the scaling part you mentioned, the first thing that usually goes on a social app is the feed query, fine at 72 posts, slow at 70k if it has no limit or the sort column isn’t indexed. worth adding a LIMIT and checking that index now while it’s cheap
Thanks!! 😭 Yeah, removing Widewave was a tough call, but the UI was getting confusing, so I had to do it.
And thanks for the scaling tip! I’ll look into the feed query, LIMIT, and indexing before the number of posts grows. Better to handle these things early than struggle with them later!!
'They look outside the window and see Crowdwide's features' made me laugh out loud. Cutting features you built hurts more than building them, so respect for doing it on day 25 instead of day 250. Which feature was hardest to hide?
The hardest one to remove was Widewave. 😅 I spent the most time building it because I wanted to create something similar to Reddit, but it didn’t really work out for Crowdwide and made the platform more complex. So, based on the suggestions I received, I decided to remove it. the hardest part was hiding features I had spent hours building, especially the ones I thought would make Crowdwide stand out. But I realised that a cleaner UI with fewer distractions is better than a UI packed with features. Better to simplify now than regret it on day 250
The split between joining communities in the dashboard and creating one from your own community page is worth a quick findability test. Ask a first-time user to create a community without pointing them toward the menu, and note where they look before they succeed. Hiding post options in a dropdown can reduce clutter, but the primary creation path still needs a visible clue. With 18 members, a few observed attempts can give more useful feedback than a click-rate comparison.
That’s a really good point! I’ll definitely keep this in mind and try testing the flow with a few first-time users to see where they get stuck. Thanks for the suggestion, Marcus! 🙌
Mention me @technogamerz 🤣
DONE 😎 :D
Hey, superstar Thanks 😊
😁😎
😊
Mention me bro me too suggested 🥲
DONE!! :D
Thanks 👍🙂
🙌🙌
18 members
72 posts shared
4 communities
Really impressive 👏🏻
Thank you didi :D