No longer do you have to wait your turn while someone shares their screen - every user can share their own app anytime they wish. It also makes for a fundamentally more interactive (and vastly improved) user experience. Multiple people can share individual windows just by clicking on a tab above each window or by dragging them to the shared screen. Perhaps the biggest improvement is that you aren’t restricted to sharing one person’s entire screen. Not only does it do everything Screenhero did (and faster!), but it also offers a superior collaboration experience and is packed with innovative new features. But rather than waiting for this long-dead hero to rise from the grave, developers can instead lean on CoScreen to meet their needs in a new way. The (Screen-Sharing) Hero Developers Need Right Now Don Goodman-Wilson, one of the original developers of Screenhero, called CoScreen “game-changing” and now even works with them.ĭevelopers still yearn for the return of Screenhero. Most of the competition has just emulated what made Screenhero popular, without adding anything new. Stand-alone substitutes have emerged in its place, but nothing has been quite the same. Interest in the screen-sharing service on Slack floundered, and it was eventually removed entirely.ĭevelopers all over the internet lamented Screenhero’s loss. ![]() Worst of all was that it lost multiplayer support, and users complained that it wasn’t as bandwidth-efficient.Īnd, while many of us use and love Slack on a daily basis, no one uses it for its video chat or screen-sharing. They intended to rebuild all of the features directly into the Slack app to offer a more efficient experience, but developers decried the new integration. It didn’t take over your whole screen like other video services, either.īut then in 2015, Slack acquired Screenhero, and then discontinued the stand-alone service. Clients could modify a project a developer was working on, or two developers could code together. Not only could two people share a screen, but both could also control it with their own mouse. Screenhero 2013 (Source: Screenhero/Slack) ![]() Screenhero removed that hurdle and allowed developers to work nearly in real time, using any app they could think of, which was a game-changer upon its release in 2013. But it wasn’t exactly an intuitive system, unless you really knew your Linux commands. The best solution was possibly tmux, which allowed users on Unix-like systems to access multiple terminal sessions. When the World Lost Screenheroīefore Screenhero, remote developers had to work using video chat and screen-sharing tools that didn’t encourage collaboration. It’s packed with features that tackle the needs of remote teams through an entirely new concept. ![]() ![]() It made a lot of work that much faster, and was specifically good for pair programming and for presenting to clients.ĬoScreen provides people with everything they loved about Screenhero - just improved in nearly every way. With it, you could collaborate in real time and with any app you had on your computer. You both were able to use your own mouse to interact with the application, making it specifically designed for remote teams. If you never got to use Screenhero, there was a reason why it became so popular: It was a tool that let its user screen-share any of your applications with any collaborator over the internet. Fortunately, we here at CoScreen have built a brand-new tool that does everything Screenhero did (and more). Screenhero was an online collaboration tool like nothing else, right up until Slack discontinued it in 2017, leaving a void in the programming world.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |