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: Pop.com – pair programming with low-latency, Screenhero-style sharing
Related anecdote: Screenhero's UI was originally totally native on the two platforms we supported (Mac and Windows). It was a night-and-day improvement (it looked better, had fewer bugs, was easier to build and maintain) when we moved from native UI to HTML5 (using Awesomium on Windows, and WebView on Mac). However, we'd then have issues on Mac where a user's UI would have glitches because their version of OS X or Safari (often both) weren't up-to-date. So it was always a little awkward to tell people that the reason their screen sharing app looked funny was because they needed to update their web browser.

Having said this, I think this discussion between Electron vs. Native is a false dichotomy. Performance and developer efficiency are both clearly important, and we don't have to maximize one dimension alone. I am confident we'll find a way to make Electron far more performant by switching off unnecessary features, such that it provides us just the surface area we need to be able to build great products that are indistinguishable from their native counterparts: except that they're quicker to build, easier to debug, are of higher quality (with fewer bugs), and cost less.

I know this sounds optimistic, but given the popularity of Electron, coupled with the issue of performance, this is an issue that is certainly going to improve over the coming months and years. Who knows, since ours is one of the more performance-hungry products, we may end up finding a solution that others can leverage as well.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
We're pushing out a fix for the back button as I speak, thanks for the heads up! It should be live in ~10 minutes (CI build + test + deploy).

Discord: we haven't looked into their API yet, but it's an oversight on our part. We'll take a look soon!

Pricing: thanks for the detailed explanation of where you're coming from. Your perspective resonates well with ours, which is that we'd like the amount our customers pay us to be roughly commensurate with the value we provide them.

If you're truly interested in using Pop and providing feedback, I'd love to learn more about your team and your background so we can make sure we're aware of that perspective as we work on our pricing plan. Feel free to find a time via https://calendly.com/j-pop/30min or drop me a line at j@pop.com. Thanks!

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Thanks for the heads up on Firefox/iOS — we'll take a look!

Your repertoire of skills is crazy impressive — it's really inspiring and amazing to see all the stuff you've built and work you've done. Your manifesto is also exactly the kind of thing the world needs more of. We're not currently hiring but I would love to chat with you to exchange notes and war stories if you're up for it! Feel free to grab a slot via https://calendly.com/j-pop/30min :)

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
We could actually build this — drop us a line at hello@pop.com and let's talk through exactly how this could work with Slack + Pop!
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
This is now fixed, thanks for the heads up!
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
This is now fixed, thanks for the heads up!
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
This is a really fair point, and we will look into seeing what we can do to alleviate this resource usage when in the background.
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Agreed!

After starting with screen.so, we realized firsthand the importance of having a name that's easy to remember and communicate.

Also, instead of viewing the domain as an expense, it's more of an enduring asset, which potentially increases its value over time.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
This is a good point. We definitely want it to be a no-brainer for people to keep Pop running. One idea may be for us to look into relinquishing resources while running in the background, which could be a best of both worlds solution.
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Wow, that's great to hear! Please do let us know about the random hiccups at hello@pop.com, since the long tail of issues is surprisingly long in this product space, and so we really appreciate any feedback that can help us improve.
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Our core business is enabling remote work and remote pair programming. WebRTC infrastructure is largely commoditized, and we're open to revisiting how we handle our WebRTC infrastructure in the future.

Daily is a great infrastructure provider, and moreover, the team was incredible to work with.

The reason we switched out from Daily was because we were running into bugs in the product, and weren't able to tell whether they were on our end or Daily's end. By owning our own infrastructure, this became a non-issue: every bug was ours to find and fix. It turns out most of the issues we had were bugs in our custom modifications to Electron to reduce screen share latency, but we had no way of knowing at the time. Now that we've invested in our own infrastructure, it's the path of least resistance to continue using it, but we're open to revisiting this decision in the future.

The Daily team is stellar to work with, and I strongly recommend them to anyone looking for a WebRTC infrastructure provider.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Thanks for the feedback! You're right, we need to improve each of these significantly.

Reduce Power When Idle: decreases the frame rate from 30fps gradually down to 15fps when there's no user activity after a few seconds, and also drops frame rate due to CPU utilization. But you're right, we need to rethink this.

Resolutions: yes, it does scale down to 1x, and yes, selecting a resolution would be better.

Re: shortcuts, do you remember when it was that you experienced these issues? We had a few bugs around these that have been fixed. We're also working on a revamp of our keyboard handling code for all three platforms to address some of the remaining issues. If you're still running into a specific issue, let us know via hello@pop.com and we'll make sure it's fixed in our keyboard overhaul.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Wow, thanks for sharing, and for the detailed write up! Please keep the feedback coming (I'm j@pop.com if you'd like to keep in touch in the future).

I do agree Screenhero should have had a more generous free tier. With Pop, we will likely have a free usage tier when we start charging. We haven't mentioned it on the pricing page just yet since everything is currently free and it would complicate the story.

I love the analogy you've made with Adobe Acrobat Reader! We definitely want Pop to become the default tool you'll use when you want to work remotely with someone on a task together on your computer (pair programming today, but a whole lot more in the future). And I agree that keeping a generous free tier will help us enable that, beyond just the ability to join calls started by paid users.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
This is a great point. We'll add support for this soon, thanks for the idea!

We actually have a developer console command you can type to achieve this today if you really need something ASAP:

- In the desktop app, click the hamburger menu, and then click the Pop logo 8x to launch Dev Tools

- In the console, type setBandwidth(1000) to set the max and min bandwidth to 1000kbps. You can type resetBandwidth() to undo the change.

If this doesn't work for you, please email us at hello@pop.com to let us know.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
We have tinkered with the idea of a native module solely responsible for screen scrape + encode + send, which would further improve performance.

Also worth noting is that there's a setting to "reduce power when idle", which throttles screen scraping frame rate when relative CPU utilization is high. Additionally, you can disable "Use full resolution" to turn off Retina support, which should further improve performance for you. We'll work on surfacing these settings better, since it's not obvious that they're buried inside the settings page.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Yes! Once it's available in WebRTC, we'll implement end-to-end encryption for group calls. There is progress being made in this direction: https://webrtchacks.com/true-end-to-end-encryption-with-webr...
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Thanks! Discussed here: https://news.ycombinator.com/item?id=28225447
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
When you say Pop could be more lightweight, are you talking about CPU or memory usage?

Also, do you keep Slack / Microsoft Teams / Dropbox / 1Password / VSCode always running, and do you have the same concern with those apps or is it something unique to Pop?

Performance is definitely a priority for us, so understanding where you're feeling the bloat would be really helpful to us.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
It wasn’t ever intended to be a buy-and-kill, it’s just unfortunately what ended up happening. When Slack acquired Screenhero, it was with the full intent to bring voice/video/screen sharing to Slack. The problem was that, post-acquisition, leadership lost interest in what could’ve been a promising feature set and growth vector for Slack (see: Zoom in 2020). Partially because integrating disparate pieces of software is a hard problem and partially because management's appetite for investment in the team waned after the first year, building Slack Calls was slow and it was unclear how valuable the feature was to Slack's success. Add in the cost of maintaining what is a very complicated and far-reaching implementation for interactive screen sharing, (not just for engineering, but also for policy/legal and customer support), it made sense for Slack to kill it.

While I was still at Slack, there were retrospective conversations around how Screenhero maybe should have been built on the Slack platform, instead of as a first-party app. However, the acquisition happened so early in the life of Slack that the platform didn't really exist yet, so it's unclear how we'd do better if we had to do it all over.

With Pop, we're doing things the right way. Pop is a standalone app, with a solid Slack integration. It makes it really fast to jump between the two (in fact, it's faster to jump into a Pop meeting via Slack, than it is to join a Slack Call!).

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Hopefully we can fill the Screenhero-shaped void in your toolbox with Pop. Please do try it and let us know what you think! We're committed to making Pop exceed Screenhero in both functionality and longevity.
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Thanks!

I worked with https://news.ycombinator.com/user?id=ted0 who was AMAZING at helping find and acquire the domain. I can strongly recommend him as an amazing person to work with. It took a few days to find a domain we loved, and another few days to close the transaction. It was quite an interesting experience!

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
We heard an equal number of people excited about being able to jump into a call with a coworker, vs. being worried about yet another layer of distraction. Having said that, we've now built out most of the infrastructure to support that feature (we have a contact list with your team in it), so we'll be looking into this soon.
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Sending over keystrokes will always be faster than sending across a video stream of your screen. So VSCode Live Share will always be faster. However, in practice, we've found the cost of a few extra milliseconds in latency are far outweighed most of the time by the benefit of being able to interact with any application on the shared screen (and draw).

For instance, if you're building a webapp, and need to look at the product alongside the code, screen sharing (especially with the ability to draw) is a lot more valuable than being able to type in the IDE.

Back when we made Screenhero, we had the option to share a specific app, and what our users told us was that they'd often start by sharing the IDE, but then realize they wanted a lot more, and so would have to stop and share the entire screen. We eventually dropped the 'window share' feature for this reason.

jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
I'm explicitly not taking funding for Pop for this exact reason: I want to keep Pop around forever. I know that isn't something most people are able to do, and I'm grateful for my past success that's enabled me to do this. But I can tell you that it was incredibly sad for me to see Screenhero die, and I never want that to happen again — both as a founder, but also as a user.
jsherwani··on Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
Hello HN! I’m the founder of Pop (https://pop.com) and formerly the co-founder and CEO of Screenhero. Also on the team are a couple other ex-Slack folks and a former Electron co-maintainer.

Pop is the spiritual successor to Screenhero and strives toward the same goal: making remote work better than working together in the same room. After Slack acquired and subsequently killed Screenhero and after becoming remote workers ourselves, we found that none of the Screenhero copycats were really solving the problem adequately. Some are unstable, some are slow, some have poor UX. We decided to get back into the space and build a product that we like to use, leveraging some of the good ideas we came up with working on Screenhero and Slack.

With Pop, instead of just talking with your coworkers about concepts with words, the shared screen becomes a shared whiteboard for diagrams and flow charts. Instead of barking out line numbers or function names, it’s faster to highlight the line with a mouse. And instead of telling someone what to type, it’s easier to just show them by typing directly in their text editor. You can start a call directly in the app or with the Slack integration “/pop” command and collaborate with coworkers on macOS, Windows, and Linux. Or, if you don’t want to bother someone to download the app, they can join a session via web browser (mobile browsers supported, too!), even without a Pop account.

For now, it’s completely free to use. We plan to always maintain a free version, though for heavier team and enterprise use, we’re looking to start charging soon (servers are very much not free). Once we have revenue, we plan to turn some of our attention to adding more remote office features, like spatial audio and presence, and, more broadly, addressing issues of isolation and loneliness in remote work.

We’ve bootstrapped the company entirely ourselves and are unbeholden to outside investors. Our goal is to build a product that people enjoy using. We’re not looking for an exit; we’ve been through that and know what it’s like (financially great, but emotionally taxing). We want to create an independent and sustainable company where we are happy to work for our entire careers.

Let’s get these out of the way:

1. Yes, we’re building on Electron. Yes, we are aware of the performance tradeoffs, but have decided this is the best choice for us. We’re shipping Windows, Mac and Linux clients along with browsers with a four-person team — it’s the only good way right now to do that without features taking six months. We’ve modified the screen sharing pipeline in Chromium to reduce latency as much as possible, because with interactive screen sharing, milliseconds matter.

2. Yes, the domain was expensive. Roughly $1.5m. We consider it an asset that is unlikely to depreciate significantly. (The domain actually has an interesting history as a failed precursor to Netflix from Ron Howard and Steven Spielberg https://www.theguardian.com/technology/2000/sep/10/internet....)

3. No, our non-compete no longer applies — it expired two years after Slack’s ScreenHero acquisition.

4. Yes, we were originally called Screen.so. It was not a good name (and HN let us know, thanks!) and we are now very happy with Pop.

We’d love you to try Pop and let us know what you think, even and especially if it doesn’t work well for you. The app has gotten exponentially better because our dedicated users tell us about their issues and work with us to get them fixed. And, if you have ideas about how remote work could be more enjoyable, we’re eagerly listening!

jsherwani··on Ask HN: What tangible benefits did you get from spending time on HN?
In December 2012, one of our early alpha users of Screenhero posted the product to HN. It catapulted us into the public beta phase, and got us our initial traction. Those users eventually helped us refine the product over a year and a half to get it to revenue, profitability and eventually, our acquisition by Slack.

Almost a year ago, I posted my new startup (https://screen.so) to HN, and got a similar group of amazing users that have been helping us slowly but surely improve the product. We’ve now got a number of household-name companies using us on a daily basis.

It’s also my favorite site to visit every day in the hope of learning something new. There’s nothing quite like it.

So yes, HN has changed my life multiple times. Kudos to the community and to dang and others who make this site as awesome as it is on a daily basis.

I have, admittedly, gotten zero wives directly through HN!

jsherwani··on Ask HN: What tangible benefits did you get from spending time on HN?
Thank you for this gem and the responses. I haven’t laughed out loud from something I’ve read on HN as much as I just did thanks to this comment and its children comments.

Even though I got zero wives out of these comments, there was some real value generated here!

jsherwani··on Delphi Method
Very cool, how does the team use this method as part of its prediction process?

(Also: Roni, the head of this research group, was my PhD thesis advisor more than ten years ago!)

jsherwani··on Thanks HN: You helped save a company that now helps thousands make a living
Additionally, I think that tools like Webflow empower devs as well. Why spend hours writing a custom piece of code when it can be done in Webflow in a fraction of the time, and potentially even handed off to a non-dev to manage/maintain.
jsherwani··on Show HN: Pop.com – Video Calls, in 3D
Sorry, this looks like a bug! We will try to fix it soon (likely after the holidays).
← PreviousPage 2 of 7Next →