Solo maker with a bunch of separate products — one community or one per product?

Ok so i'm a solo maker and over the years i've ended up with way too many small products lol — some react/ui libraries, a few native mac apps, some cli stuff and plugins. same guy behind all of them (me) but honestly each one lives its own life: own site, own release cycle, a couple even have their own newsletter.

lately people keep asking me "ok but where do i report bugs / ask for features / just hang out" and tbh i don't have a good answer yet.

the thing i keep flip-flopping on: the dev-library crowd and the mac-app crowd barely overlap. a dev debugging a component wants a totally different vibe than someone using a little menu-bar app. so part of me wants to split them... but i'm a one man band and the idea of babysitting multiple half-dead rooms kinda terrifies me.

rn i'm leaning towards a single discord with a few channels grouped by product type, instead of one space per product. but i've never run a community at this scale solo so i'm mostly guessing here.

so for anyone who's done this across several products on their own — did you keep everything under one roof or split it? discord or slack for a dev/maker crowd? and what's the one thing you'd do differently if you started over?

would love to hear real experiences, not just theory 🙏

15 views

Add a comment

Replies

Best

I did probably keep one Discord community with separate channels for each product It feels easier to manage and still gives each product its own space