1,473 karma · joined July 14, 2009
Now building pop (https://pop.com).
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.
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.
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.
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.
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!
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.
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?
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.
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.
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!
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.
Admittedly, we only had a handful of Linux users in our private beta, but still, none of them mentioned the GNU tool.
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!
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.