I’ve been working at a fully distributed company for 3 years and I can tell you with a high degree of certainty that none of my 700+ coworkers will ever use something like this. You may find some traction now with companies abruptly transitioning to remote work and not having a clue how to get work done without being in an office, but long term, I’m a sceptic. I can tell you, however, that I would absolutely consider…
Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
141–150 of 234 posts
Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#142The writeup above keeps talking about a “room” but the website features only person-to-person with the exception of the illustration of muting which shows the guitarist and hand-clapper as two ‘windows’. So two people cuts the 1080p (pretty low res) screen in half. What about 10 people, or 25?
The answer is not in your FAQ:
Q. How many Sidekicks can be connected on a team?
A. We built Sidekick to handle teams of all sizes.
You shouldn’t even have included that Q/A in the list, if you’re not going to answer it!
Microsoft, Zoom, others, all working to figure out how to show more team members at once, so presumably this isn’t trivial to do well. Nothing indicating how you solve it, what to expect with larger teams, and what’s the present design intent to set expectations.
So, real questions from a potential team, and team-of-teams (8-12 people per team, 20 teams):
What’s the maximum number of participants that display at once, and what happens beyond that number?
Regardless of design intent, what’s the actual maximum number?
Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#143Congratulations on the launch. I'm a remote worker, so I was keenly interested in this. I've been using a Facebook Portal for about 1.5 years as an always-on video device. It works great, so I love the idea. There's open water in this space, so it's great to see others entering it. For now, I don't see why I would ever use this over the Portal. The Portal HW has a high-quality build with a great speaker, and the auto…
That's really cool! Have you expanded beyond your cofounders? And are you guys still using it for always-on? Also, how do you guys handle knowing when you can talk to the other person? How do you know if the other person is in a meeting?
We haven't, although we do have other team members with Portals, I don't think it would be effective for our use case. Most of the conversations are semi-private, so we use the device like we were sharing an office more than having a meeting.
As a team, we use Slack for Chat, Zoom for Meetings and screen sharing, and Slack for one on one video chat. We use slack for quick conversations because its fast to deploy, and you can keep your hands on your keyboard (or mouse).
Oddly, we hop on Zoom all the time for screen sharing but continue to just use the Portal for AV.
"Also, how do you guys handle knowing when you can talk to the other person?"
That's have been easy. If I want to talk to Tom, I just look at him. If he's in a meeting, I can almost always tell. We keep each other muted unless we're going to talk. You can tell from the eyes, or headset, etc. pretty quickly.
For the shared office use case, in particular, it's excellent.
Any way you slice it, I'm glad to see more people in this space, as it can only lead to better things for remote workers. Good luck!
Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#144Earlier quoted context omitted.
> One downside is dramatically less collaboration. This is simply an excuse for why remote doesn't work. It's a dead horse. If you find yourself collaborating less as a result of remote work, then I question your remote setup and culture. > If this could help create more of a spontaneous back and forth in-person feel. I actually feel less shitty by spontaneously reaching out to my colleagues via Slack or by phone whe…
Thanks for the feedback, we're still really early so this datapoint is really helpful. Sidekick works really well for teams that need to be always communicating real-time. This isn't all remote teams, but the subset that needs this is underserved and we're trying to help with Sidekick.
Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#145For the sake of mental health and privacy, I hope this product crashes and burns.
Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#146The only question I have is how well it scales. The writeup above keeps talking about a “room” but the website features only person-to-person with the exception of the illustration of muting which shows the guitarist and hand-clapper as two ‘windows’. So two people cuts the 1080p (pretty low res) screen in half. What about 10 people, or 25? The answer is not in your FAQ: Q. How many Sidekicks can be connected on a te…
However, I also believe that 3-5 is roughly the amount of people who you actually work really closely with. These units are probably the right grouping for who is in one room.
There is no actual max number, but I do think the design and the use case would fall apart right now. But there's some things we're thinking about like separate channels that might help with this.
Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#147I think a device approach is reasonable. People like a device. They tend to not like a bunch of devices, which is why smartphones became so popular. But since this is something that would basically be a desk accessory, it might work.
One thing to be careful of, though, is that C-suite folks will often project their workflows onto their employees. What I see particularly hard-hit, is respect for "The Flow." This is that "magic productivity sauce" that comes from uninterrupted working time. Managers and executives have very little of this, but it is vital -vital- for engineers and creatives (I was a manager for a very long time, and the most valuable thing I did, was act as a buffer between sources of interruption, and my team).
Nowadays, the absolute worst thing that can happen, is I get a phone call or messaging interruption, while I'm chasing down a bug, or learning a new technique. It makes me blow my top. I tend to be rather abrupt, when answering those calls. Especially since the vast majority are robocalls, and I plonk them immediately (even that little interruption is painful).
I'd say that maybe having some published "best practices" to accompany it, might help. Maybe a blog -vlog?- that is accessible from these devices, could be nice.
Of course, it goes without saying that responsiveness (less than 500ms latency) and frictionless infrastructure is also vital for everyone, but I assume that is already there.
Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#148The way I see it, being "always on" is one of the worst things about office work. Always on is a constant distraction from doing good concentrated work. I think off by default is a far better paradigm for remote communication tools.
Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#149Re: Launch HN: Sidekick (YC S20) – A hardware device to connect remote teams
#150The way I see it, being "always on" is one of the worst things about office work. Always on is a constant distraction from doing good concentrated work. I think off by default is a far better paradigm for remote communication tools.