What is Reddit's opinion of Clubhouse.io?

From 3.5 billion Reddit comments

Jira was way too complex and required too much setup. We eventually landed on clubhouse.io after trying a whole bunch of options. We feel that it struck the right balance between lightness, structure, and flexibility.

My absolute favourite has been: https://clubhouse.io/

​

We tried Gitlab issues, Asana and Jira and were always a little unhappy. Clubhouse has been wonderful for us and has helped to visualize our operational bottlenecks.

​

PM me for a referral code if you want the extra two months free.

I've poked around with Clubhouse.io, but I've never seriously used it. The impression that I got, however, was that they (like a lot of tools) try to offer a lot of things for a lot of people who may be using it in different contexts.

In your context, as a hobby project, you may not need different projects. I can see it being useful for a larger team who wants to separate out discovery work from delivery work from operational/maintenance work and have different workflows for each one. It can also be useful as another way to slice work that is closely related for tracking purposes.

I'd think that Milestones/Epics/Stories would be sufficient for your use case and you can set up a single project (just because it's a requirement of Clubhouse).

Thank you u/DeusExMagikarpa for the resources. I agree in the clubhouse.io case, it doesn't make sense to use a subdomain. I think when the end user is interacting with the product itself, a path definition of the company would suffice. I think when the end user is expecting to be interacting through another company, a subdomain of that company makes sense (like in the restaurant online ordering case).

My use case is more in like with the restaurant online ordering. But you certainly pointed me in the right direction with multi tenancy and I think I can run with it from here! Thanks again!

Oh there's a different Clubhouse (https://clubhouse.io/) that isn't the "drop in audio" app that is all the hotness in Silicon Valley right now. I was confused for at first.
A few suggestions for what you've brought up:

- Hold retrospectives with your team to tweak your process and improve. If you only do one thing, I'd recommend this.
- Have cards link out to a document that can be more detailed or be easier to update. This can be a feature outline or a QA doc or a diagram. Whatever works for you.
- Break cards down until they're atomic enough to estimate
- Have separate cards for integration and other tasks that you know will take time. Even if you don't have the integration work needed upfront, you can often put in placeholders with estimations that you refine later

clubhouse.io found this gem in may and its been amazing. completely free and honestly beautiful and makes me want to complete my tickets cuz its so pretty and fun compared to jira & trello

https://clubhouse.io/ easier and more pleasant to use than jira, more powerful than Trello. https://uptimerobot.com/ For monitoring websites and apis for uptime and sending notifications if they are down

Cool, I didn't know that existed.

For anyone else new to the term, here is the info.

>A developer evangelist is first and foremost a translator. Someone who can explain technology to different audiences to get their support for a certain product or technology. It needs to be someone who is technical but also capable to find the story in a technical message… A good developer evangelist can get techies excited about a product by pointing out the benefits for developers who use the product on an eye-to-eye level.

>Christian Heilmann, Principal Technical Evangelist at Mozilla

I found links in your comment that were not hyperlinked:

• Clubhouse.io

I did the honors for you.

^delete ^| ^information ^| ^<3

Clubhouse.io sounds like exactly what you're looking for and has a free plan

https://clubhouse.io/

Has a Kanban view, similar to Trello with the ability to deep dive with epics, due dates etc like Jira without all the feature bloat and setup cost Jira comes with.

You might want to add Clubhouse (https://clubhouse.io) to your list. We've just switched to it at my work, and it runs circles around JIRA for our use case (smallish SaaS startup, but it would also have been excellent for agencies I've worked at before).

I've always felt like I was working against JIRA, but Clubhouse feels like it more less just represents how we were already working.

Not exactly related to Laravel, but we've been using Clubhouse to great success recently. It's free for up to 10 users, so easy to trial if you are a smaller team. It's like a mix of Trello and Jira, and suits our needs well so far.

Referral link if you would like to sign up!

Wir nehmen clubhouse.io in der Firma.

Gefällt mir so gut, ich würds sogar zuhause benutzen und es gibt auch ne app dafür.

Falls du aber selbst lokal hosten willst, dann würd ich (wie andere schon sagten) gitea.io nehmen. Das lässt sich übelst einfach via docker oder nativ hosten und hat einticketsystem drin.

Thanks for the reply! Clubhouse.io seems awesome def seems the closest to what im looking for, im sad they dont have time tracking but it enables third party integration. I like that clubhouse has velocity reports.

Thats something I definetly require.

Notion also came up but doesn't have reports at all.

Do you use any time tracking plugin for <strong>clubhouse.io</strong>?

Young parents aren't markets. They're your customers.

Gaming, AR/VR, Semiconductors, Healthcare, Logisitics are markets.

Market Size = totat number of customers x revenue per customer = total revenue that can be earned

If you want to find a 'hot' market, look at these metrics:

- TAM - Total size of the market. Something around 30B will do. TAM < 10B is not a good market. It is a vanity metric, but is to quickly shortlist.

- Target Market : Basically the people who will first buy the product. This market > 1B. (Rule of thumb)

- CAGR and YOY: This and target market are by far your most important markets. CAGR is basically growth. A hot market is a market that's growing extremely fast. Gaming's CAGR is around 30% which is one of the fastest growing markets.

Source : I'm an ex-CEO and this is what VC's care about. They've have told me this.

All of these can give you a rough idea on how much money you can make, but I would suggest you follow this process

- Choose a market you know well and know is kinda hot (Use your gut feeling / Do some basic research on google and see what products are VC's talking about) For example right now it's better ways to communicate remotely - clubhouse.io is making waves

- Find a problem in the market and VALIDATE. Do not build anything. Just talk to potential customers and find out. Use the mom test. Talk to as many customers and find out if they have a problem and find out how much will they save.

- If you get a good response, only then start building.

Note that if you run Django behind a more general Webserver (e.g. Nginx), then you can return headers that tell Nginx to return the file.

E.g. like this (random Google hit): https://clubhouse.io/developer-how-to/how-to-use-internal-redirects-in-nginx/

Nginx is good at serving files. Frees up Django for the stuff it is good at.

Clubhouse is hiring Clojure backend and JS frontend developers. We are a distributed company, with > 50% of folks working remotely. See https://clubhouse.io/careers/ for details.