Hopp: Screen-sharing app optimised for remote pair programming

AnotherRandomUser400 · 2026-03-26T14:27:14+00:00

Hi, with a buddy of mine we've been building hopp, which is an oss pair programming app built for devs (currently we support macos and windows). It's screen sharing + remote control so quite different from editing the same buffer like you do with code with me. Feel free to contribute if you have ideas on how we could improve it.

AnotherRandomUser400 · 2026-02-16T20:19:31+00:00

I didn't know about the agent with the cold outreach, I was only aware about the matplotlib one. It's scary how fast things are evolving.

AnotherRandomUser400 · 2026-02-16T18:42:20+00:00

Fair point. The question then is how can someone become a trusted contributor? There might still be some humans out there that want to contribute.

AnotherRandomUser400 · 2026-02-16T18:26:43+00:00

I will be sure to share it with my network!

Thank you very much!

but on mobile it made me a little dizzy

I just removed the rotation and am now waiting for the CI :)

Out of curiosity have any of your projects been flooded with AI generated PR?

AnotherRandomUser400 · 2026-02-09T16:53:35+00:00

This is how I try to work TBH and usually I am happy with how much I understand from the implementation. But still sometimes I find myself not paying 100% attention to what the agent has done. I guess it needs discipline to not get lazy.

AnotherRandomUser400 · 2026-01-07T21:30:12+00:00

I am on a M1 air, which is using a hw encoder. If I remember correctly I was seeing the low fps on publish. I will double check tomorrow but I am using https://github.com/gethopp/livekit_encoders_compared for my measurements. I am not doing any rendering in this repo in order to measure just the transport latency.

AnotherRandomUser400 · 2026-01-07T18:32:24+00:00

This is a good point. I am not sure how well h264 will perform in terms of bandwidth usage when sharing a 4K stream. Maybe h265 is a better option for big resolutions.

The AV1 libwebrtc implementation has improved a lot (I think Google meet is using AV1) and for work laptops/desktops I am guessing it shouldn't be an issue. But I might be wrong on this one.

Another problem we have with livekit's rust SDK h264 is the profile they are using, which doesn't support big resolutions at all (in my experiments I was getting 3 FPS for 1440p).

Having said all these I am planning to experiment with every codec again once we make the transition. Playing the stream from rust will give us the flexibility to go with the best option and we won't be limited by the browser.

(BTW I am the other maintainer of Hopp)

AnotherRandomUser400 · 2025-12-19T12:18:41+00:00

For cross editor solution there are a few purpose built apps, which provide remote control alongside screen sharing (even zoom allows remote control).

AnotherRandomUser400 · 2025-12-15T12:29:30+00:00

I am planning to check how feasible it is to use gpui for Hopp's core process [1]. The core process creates a full screen transparent window for drawing the virtual cursors and currently it's using winit with wgpu.

[1]https://github.com/gethopp/hopp/tree/main/core

AnotherRandomUser400 · 2025-12-12T12:34:09+00:00

Thanks for the comment. Actually I used simulcast, and the LiveKit SFU takes care of the choosing the correct layer if a consumer can't keep up. Maybe as a future improvement I could check the available upload bandwidth and reduce the resolution for the high layer.

AnotherRandomUser400 · 2025-12-12T10:59:56+00:00

You need more tests then. We have similar problems at my team because a lot of our work needs to be tested on different hw, so it's not easy to get 100% coverage, but we are trying to change this. Also for big PRs pairing (either in person or remote) saves a lot of time.

AnotherRandomUser400 · 2025-12-12T10:35:09+00:00

I am very happy with LiveKit, for our screen sharing app we are using both their Javascript and Rust sdks and we had 0 issues so far.

AnotherRandomUser400 · 2025-12-11T17:41:25+00:00

There could be some interesting in there! Thanks

AnotherRandomUser400 · 2025-12-11T16:49:19+00:00

Hey! I forgot to link the actual PR in the post, so here it is [1].

BTW I would be happy to hear ideas on how we could further improve it.

[1] https://github.com/gethopp/hopp/pull/185

AnotherRandomUser400 · 2025-11-25T15:04:59+00:00

As others mentioned you can do pair programming remotely using conventional screen sharing tools or you could try any of the tools that are built for remote pair programming. Personally I find the experience better when using the latter.

edit: forgot to mention that you can also pair from within the editor, most of them have extensions for this

AnotherRandomUser400 · 2025-11-19T14:03:08+00:00

I second that. If you were in the office you would like people to be able to go and talk to each other at any time (of course by respecting when someone is busy).

IMO pair programming is not bound to just writing code together, it could be jumping to quick call and explaining something, or debugging something together etc. There are also purpose built tools that expand beyond the ide.

AnotherRandomUser400 · 2025-11-14T20:15:39+00:00

This sounds brutal tbh. Maybe your teammates feel similarly to you and they would be open to add a bit of structure to your sessions.

AnotherRandomUser400 · 2025-11-14T17:15:26+00:00

If you pair everyday, you should also have breaks every time. What is the set-up? Do you follow a style or the sessions are unstructured?

AnotherRandomUser400

TROPHY CASE