HNHacker News
TopNewBestAskShowJobs

jsherwani

1,473 karma · joined July 14, 2009

Co-Founder/CEO Screenhero (YC W13, acquired by Slack).

Now building pop (https://pop.com).

submissionscomments
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Looks great! :D
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
FWIW, I believe life’s too short to be doing the same thing over again. I’m building Screen because I want to see where we can take it independently, as I think we had some great ideas that weren’t able to see the light of day. Screen is already a far more useful product IMO than Screenhero was.

Having experienced an acquisition, there’s not much value in going through the same experience again.

What’s personally interesting to me is: can we make something that helps all knowledge workers work together remotely in a way that they couldn’t before? We were onto something with Screenhero, and I’m excited at the chance of following that thread again, and seeing where it takes us!

Having said that, I know trust takes time to build, and I hope to prove this to you with actions rather than words.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Happy to hear that! :D
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
As long as you can make a network connection between the two hosts (either directly or mediated via a server in the middle), you should be fine. We haven’t tested specifically between China and the US, though.
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
You may be able to install and run Screen on Windows, although to be 100% honest, we haven’t spent a lot of time outside the assumption that the user has the access they need. If you can drop us an email at team@screen.so, one of us will make sure to follow up with you once we try it out.
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Short answer: we have no intention of ever getting acquired. We are 100% bootstrapped, and we plan to become and stay sustainable, so we can be in it for the long haul.

Also, regarding acquisitions, I’ve been there, done that, and I wouldn’t be building this company just to do the same thing again (life’s too short for that).

I love Slack as a company and as a product (I spend many hours in it daily). However, in hindsight, it’s not possible to integrate one complex piece of software into another complex piece of software. We ended up with a union of two separate sets of constraints (from each product) which made it impossible to make it all work. We didn’t know this when we started. I really value my experience at Slack, and it was through that experience that I learnt this lesson, along with many others, that have helped us make Screen what it is today.

For Screenhero users, I feel that with Screen being publicly available today, the Screenhero -> Slack -> Screen transition has been one step forward, two steps back, and three steps forward again. I’m committed to continuing the forward steps from here on in.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Longer story here: https://screen.so/about

Summary: we were sustainable ($1MM ARR), but chose to join Slack since we felt we could get to our goal (have everyone use our product) faster. We didn’t foresee our product getting dropped.

This time around, the company is 100% bootstrapped, and I have no intention of taking any investment. We just want to be able to keep our burn rate low, build a product people love, and stay independent forever. I believe we can do that as long as we continue to make something people want.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Zing! I see what you did there :D
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
We’ve heard this feature request a few times, so it’ll likely make its way into the product soon.
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
I can’t speak to other products and their performance, but we’ve worked hard on performance and wide platform support (Mac, Windows, Linux apps to host screen shares, and web support for joining meetings). Do try Screen and let us know what you think!
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
There are no plans to open source our product, sorry!
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
I’ve posted a top level comment addressing this issue since it’s probably best to have the discussion in one place.

But yes, we didn’t hear from anyone in our private beta that there was any confusion regarding our name, and we ourselves completely missed the fact that GNU Screen exists with this name. I’m sorry for the confusion, and we will revisit our naming decision.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Notion was what inspired me to get our domain!
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
No need to sell kidneys... :)

Could you post this as a feature request on https://support.screen.so, along with some context to your use? That way we can follow up with more questions, others can vote for it, and we can update you on our progress. Thanks!

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Could you elaborate on why you think this is a worse reincarnation of Screenhero? Are there specific features we’re missing?

Also, there is no way to make a web app that does what Screen does. If there were, we’d have built a purely web-based app.

With Screen’s desktop app, you can share your screen TO someone on the web, but they need the app to share their screen, since multiplayer drawing and control can’t be done otherwise.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
We’d ideally like to create one or two distributions that are most widely useful, instead of having to support every single option out there — we picked Snap for this reason. Slack also supports Snap + Debian as their only two options, from what I understand.

Could you please post this as a feature request on https://support.screen.so so we can follow up with you and update you on our progress?

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
I just posted a top-level comment to address the naming issue, which a number of people have now brought up. Sorry for the confusion!
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Yeah, I can totally see how in some circles, "screen" is synonymous with GNU Screen, and that our choice of name would be confusing. Sorry about that! I’ve posted a top-level comment about the naming issue, in case more context is helpful.
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
I can see how that would be confusing. Sorry about that!

I just posted a top-level comment on the naming issue, where we were coming from, and that I’m open to changing the name.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Just to address the naming issue — we (myself and the other engineer, that comprise the entire Screen team) honestly have not used GNU Screen for more than 5 years, and didn’t even remember it existed until today’s post. I’m sorry for the oversight, but this is the point of a public beta — to help us unearth issues we may have overlooked ourselves!

I’m open to finding a new name — in fact, a few days ago, I had reached out to Slack to see if they’d be open to letting us use the Screenhero name since they’re not using it. If that doesn’t work out, and and there’s still significant distaste for the name, we’ll change it. 99.9% of the time we’ve spent to get here has been on the product, getting it to work on all the platforms it supports, and making sure it’s performant and fast. The 0.01% of time we’ve spent on getting our name and domain is something I’m happy to revisit before our GA release.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Sure!

It’s built on a private fork of Electron, but the UI is all web-based. Electron handles most of our native needs, and where it doesn’t, we have a node module to connect into the OS. A lot of our secret sauce is on the native side, but honestly, there’s a lot of complexity across the product.

If you have any specific questions, ask away!

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
We’ll look into this! Please post a bug report on https://support.screen.so so we can follow up with you with questions and update you on our progress to fix it.
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
I only decided to re-enter this space after Slack announced it was sunsetting interactive screen sharing. It ended up being too expensive a feature for Slack to support for a niche audience.

I can’t speak for the company, but I imagine they’d be happy that another collaboration tool has launched that integrates with their platform to give their customers even more choice in how they work.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
This is a really good question, and the simple answer is that Slack uses an unmodified version of Electron, and it’s not a good idea to make custom modifications to that project for such a small, niche feature. The cost/benefit just doesn’t make sense for Slack, neither to me, nor to Slack management. But Electron didn’t even exist when Screenhero was acquired, and so the constraints we eventually faced were not possible to predict when we got acquired.
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
The main market analysis was asking users what their pain points were and solving them. Screenhero didn’t have robust drawing, for instance.

Admittedly, we only had a handful of Linux users in our private beta, but still, none of them mentioned the GNU tool.

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
To be honest, I’ve never considered trademarking the name. We just want to build a product that works and is loved by its users. It’s really quite simple! :)
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
We’re a 2 person team, and neither of us uses Screen (the last time I used it was more than 5 years ago, and until HN’s response, had completely forgotten about it).

Also, nobody in our private beta mentioned GNU Screen.

A public beta helps us get feedback on issues that we have missed before, and this is one of them!

jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
I hope we exceed your expectations!
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
Screen has worked really well for us and a handful of companies that use us daily in our private beta. If you do have any issues, let us know and we’ll fix them asap!
jsherwani··on Show HN: Screen – screen sharing for remote work, by the cofounder of Screenhero
This is day 1 of our public beta, and we’re looking for feedback on things we may not have considered. The name is one such thing — based on the response, we’ll think about changing it.

The point of the intro is to convey that I’ve built a similar product before, and have experience in the videoconferencing space, and that this product builds upon the ideas of the previous products I‘ve worked on. Sorry if it came across as haughty, I didn’t mean it that way.

← PreviousPage 4 of 7Next →