aejae
Joined 8 years ago
Joined 8 years ago
For some options that work with PC, check out my other comment mentioning "Windows"
For a more better experience on both macOS and Windows, check out CoScreen as mentioned, and Tuple too!
Another tool that supports streaming to a browser is [Coduo](https://apps.apple.com/us/app/coduo-pair-coding-for-xcode/id...)... although I just noticed the single 1-star review :/
Multi is typically used for long-term teammates. That's when, the extra features we get from being native, as well as the command palette to reach someone, are more useful.
Link expires in 6 days. Most of the discussion is in the comments.
For anyone who doesn't want to load a ton of JS, in short:
# Free
Mostly pairing features. Free because we think that collaborative pairing functionality should be available to everyone, whether or not you can pay. If you're an individual contributor, you should just be able to sign up. Our closest competitor charges $30 a month for just pairing functionality, and as a result many small teams can't afford to use it.
# Standard
Mostly features to help with async communication and documentation. We think that distributed work in it's ideal is "Pair often, write a lot, and minimize meetings."
We think it makes sense to draw the paywall here because a/ The async features cost us more to run, and b/ This problem is something that team leaders or managers care about. And those are the people with credit cards.
We support teams having a mix of Free and Standard seats. Just pay for the power users.
# Enterprise
There are some features that cannot be per-seat: They have to be the whole team or nothing. For example, SSO (yes #ssoTax), API access, bespoke security review etc. For these, we can talk to the team about what their usage will look like in deciding the price.
Hope that helps. We're very open to feedback on this. DM's open at @embirico on Twitter if you have thoughts privately.
I'll be responding to the comments. LMK if you have any questions.
Seeing people using a hard-to-build feature a couple times a day, then more, until eventually you have to mute notifications to focus on work is a great way A/ to feel the progress, and B/ notice trends you can't pick out in averages.
Example for A: Just yesterday our CTO wrote in a feature-specific channel: > This page is now unreadable due to volume of usage pings! Go team!!
Example for B: Intuitively noticing whether your tool, that has say 6 DAUs on a team, is being used once by all 6 people, or in 3 pairing sessions, or something in between. Yes could run an analysis for this, but at an early stage co it's easier to just notice.
We became June users at our pre-launch co a few months ago, and the feature 0xferruccio mentioned is part of what sold me initially.
Not sure how long it'll remain useful but loving it for now.