Rendered at 04:50:48 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
Shank 10 hours ago [-]
I really want an evaluation of all of these classes of remote desktop systems and latency. Almost all of my remote display experiences have been mediocre due to lag. Maybe my tolerance is too low? How is the latency on this product?
Only RDP has felt truly responsive to me, and my understanding is that it cheats by not sending raster graphics and instead drawing primaries directly on the remote system and then updating the state based on the server?
mrheosuper 1 hours ago [-]
Sunshine/moonlight combo is still best streaming I've ever used, both in term of quality and latency. Another best thing is the client is available on many platforms.
djfergus 30 minutes ago [-]
Agree re performance and availability. However it doesn't support remote clipboard which is frustrating.
BLKNSLVR 6 hours ago [-]
That's pretty much been the only compromise I've had to make when migrating to an entirely Linux ecosystem at home. I settled on NoMachine as my pick of 'remote control desktop' software after trying a whole lot of other options (including various flavours of VNC).
Every time I use it I'm reminded of how good RDP is/was.
392 2 hours ago [-]
Have you tried Parsec?
BLKNSLVR 10 minutes ago [-]
No, I'm not sure if I've heard of that one. Will check it out.
raiseCatError 10 hours ago [-]
I agree, I have benchmarks planned for the future.
As far as the latency on MeowDisplay, In my testing on Wifi, I measured around 14-17ms median from capture to receiver handoff, not e2e. I've also seen occasional spikes around 50-90ms and some stalled frames, you do notice the stalls but overall it's pretty responsive.
I've preferred to show the cursor as it is on the mac instead of rendering it locally on the phone which may make it feel smoother but the trade-off is that it may not accurately represent where the cursor actually is on the mac if things lag or hang.
Then again, it does depend on the connection.
monster_truck 4 hours ago [-]
Assuming you are remoting into machines on your local network, I have made the Very Dumbest Compromise that I actually love, which is just leaving them connected to displays natively and creating a fake display on the controlling machine that runs a fullscreened remote desktop session set to potato. It's the only way I'll even bother to use a mac anymore, I'm not wasting another second fighting their godawful mouse input.
dabbz 9 hours ago [-]
It's uncanny, I just vibe built something super similar. A server/client system to share individual windows as a resized app on the phone. I can select certain windows to render as if it was an app on either my Windows client, mac client, or iPhone client from a windows or mac server.
Glad to know I'm not the only one thinking about this. It also connects over tailnet.
anonzzzies 6 hours ago [-]
Same here but I also replaced tailnet for our company with it as the non tech people found it too hard to use.
raiseCatError 7 hours ago [-]
Likewise, Glad to have another person thinking on similar tracks!
mpolichette 10 hours ago [-]
Since this forks opendisplay, what are you doing differently? Are you a layer on top, or a different direction?
I'd have expected that to be declared in an announcement for this community.
raiseCatError 9 hours ago [-]
Yup, I'll add a snippet in the post, thanks,
For answering your question, MeowDisplay started as a fork of OpenDisplay which had the foundations for screen capture, virtual displays, encoding and the iPhone/iPad receivers built, I've credited OpenDisplay and its developer Philip in the README under "Built on OpenDisplay"
After that, I've taken a more phone-first approach, with quite a bit of work on the interaction, streaming and security layers.
So it's built on OpenDisplay and not just a UI layer over it, MeowDisplay is going in a different direction, If you only need the core second-display experience, or compatibility that the OpenDisplay project serves better, OpenDisplay is well worth a look.
jdalgetty 10 hours ago [-]
Is this much different from Sill?
jkahrs595 4 hours ago [-]
Or RustDesk?
raiseCatError 9 hours ago [-]
The question I saw coming, and was hoping for too.
Thank you for asking!
There's quite a bit of overlap in what we're both trying to do. I've come across Sill and tried it as well, and it's nice.
I think the biggest difference for most people would be the iPhone experience across both apps. I've specifically prioritized making the whole "use your Mac from your phone" experience better, and the iPad has received the same care too, with additional customizability to make use of the extra screen space.
I've looked at quite a few remote desktop apps, how they've approached things and the trade-offs they've made, and weighed those against how I'd want MeowDisplay to do things.
Part of MeowDisplay also came from a question: why hasn't Apple done something like this natively? The iPad has Sidecar, so I've often imagined how Apple might've approached it for the iPhone, and how I'd do it based on my experience with remote desktop apps.
Coming to how they're different, I think the biggest distinctions are how I've chosen to handle Mac windows, the limited screen space on phones, and the overall UX.
Sill's optional virtual display moves the selected window onto a separate display sized for the receiver, which can resize the actual Mac window. MeowDisplay's Window view keeps the Mac window's existing size and position, adapting how it's displayed on the phone instead.
My reasoning behind this is that most desktop apps weren't designed for phone-sized windows. Resizing them can make their interfaces cramped or awkward, and I'd rather preserve their original layouts, even if that means occasionally zooming, which I find acceptable.
Sill currently focuses on displaying one window or the desktop at a time, while MeowDisplay offers a different multitasking workflow with multiple windows arranged in tabs and panes, and floating windows coming in 2.1.
Another difference is the screen space. Sill's portrait layout has the streamed picture at the top with a dedicated trackpad below it, although it also offers a Larger Picture option and direct touch.
I've questioned why we even need a separate trackpad when the whole phone is already a touch surface. MeowDisplay lets you use the displayed content itself for Direct Touch or trackpad-style input, without sacrificing a portion of the screen for a dedicated trackpad. Personally, I find that screen space too valuable to give up.
There's a difference in how you navigate through the UI as well. Sill has window thumbnails and app selection, while MeowDisplay uses Stage Peek, which you pull from the screen's edge to browse and search windows and apps, along with an expanded window overview.
So yupp, we're both trying to solve a similar problem, just with different approaches and trade-offs. I think some people might prefer Sill's approach, and others might prefer MeowDisplay's.
OsrsNeedsf2P 3 hours ago [-]
Surprised how few screenshots are in the README, given how visual of a program this is
qingcharles 8 hours ago [-]
What can I use to bring the iMessage window from my clamshut MacBook onto my Windows desktop so I can write texts on a big boy screen instead of on the phone?
hbn 8 hours ago [-]
Is there even a way to wake up a shut and sleeping MacBook? Or keep it awake at all? I'd be interested if there was that didn't have some caveat that will kill the battery.
This seems more relevant than ever in days that we're sending off an LLM prompt and then letting it chug away for who knows how long. I tend to just leave my screen on with the mouse in a hotcorner that disables the screensaver.
solyin 6 hours ago [-]
Re: battery
Al Dente.app has you covered.
raiseCatError 7 hours ago [-]
There are ways to wake a sleeping Macbook, MeowDisplay has Wake & Connect, which uses Wake-on-LAN to wake a supported Mac on the local network, provided Wake for Network Access is enabled.
It doesn't work for a fully shut-down Mac though, and remote waking over something like Tailscale isn't supported yet. That would need something already awake on the Mac's local network, like a compatible router or another device, to relay the wake request. I've been looking into that.
As for keeping it awake, macOS already lets you prevent automatic sleep whilst you're plugged into power, even with the display turned off, so you wouldn't need to leave the screen running all the time.
montjoy 8 hours ago [-]
Does this require that Apple devices use the same account like sidecar?
raiseCatError 7 hours ago [-]
Nope! You do not need same Apple ID accounts or be on the same Wifi, it has AWDL for Apple devices and a similar equivalent for Android is being looked into.
_aavaa_ 10 hours ago [-]
Cool. Does it support proper color profiles on the iPhone and HDR content?
raiseCatError 10 hours ago [-]
Not currently, haven't verified color profile accuracy on the iPhone yet, and HDR isn't supported as of now either.
iLoveOncall 10 hours ago [-]
Isn't that natively supported? I thought you could use your iPhone as side display for your Mac.
EDIT: Yes, the feature is called Sidecar.
freeli 10 hours ago [-]
Sidecar works to extend your Mac's display to iPads but does not work on iPhones.
raiseCatError 10 hours ago [-]
[dead]
SirFatty 7 hours ago [-]
VNC?
raiseCatError 7 hours ago [-]
Similar idea, but not VNC. MeowDisplay uses its own streaming and control protocols, so you need the companion Mac app.
I've considered supporting macOS's built-in Screen Sharing too, though with fewer features.
TazeTSchnitzel 10 hours ago [-]
Refreshing to see a marketing site that isn't slop.
Only RDP has felt truly responsive to me, and my understanding is that it cheats by not sending raster graphics and instead drawing primaries directly on the remote system and then updating the state based on the server?
Every time I use it I'm reminded of how good RDP is/was.
As far as the latency on MeowDisplay, In my testing on Wifi, I measured around 14-17ms median from capture to receiver handoff, not e2e. I've also seen occasional spikes around 50-90ms and some stalled frames, you do notice the stalls but overall it's pretty responsive.
I've preferred to show the cursor as it is on the mac instead of rendering it locally on the phone which may make it feel smoother but the trade-off is that it may not accurately represent where the cursor actually is on the mac if things lag or hang.
Then again, it does depend on the connection.
Glad to know I'm not the only one thinking about this. It also connects over tailnet.
I'd have expected that to be declared in an announcement for this community.
For answering your question, MeowDisplay started as a fork of OpenDisplay which had the foundations for screen capture, virtual displays, encoding and the iPhone/iPad receivers built, I've credited OpenDisplay and its developer Philip in the README under "Built on OpenDisplay"
After that, I've taken a more phone-first approach, with quite a bit of work on the interaction, streaming and security layers.
So it's built on OpenDisplay and not just a UI layer over it, MeowDisplay is going in a different direction, If you only need the core second-display experience, or compatibility that the OpenDisplay project serves better, OpenDisplay is well worth a look.
There's quite a bit of overlap in what we're both trying to do. I've come across Sill and tried it as well, and it's nice.
I think the biggest difference for most people would be the iPhone experience across both apps. I've specifically prioritized making the whole "use your Mac from your phone" experience better, and the iPad has received the same care too, with additional customizability to make use of the extra screen space.
I've looked at quite a few remote desktop apps, how they've approached things and the trade-offs they've made, and weighed those against how I'd want MeowDisplay to do things.
Part of MeowDisplay also came from a question: why hasn't Apple done something like this natively? The iPad has Sidecar, so I've often imagined how Apple might've approached it for the iPhone, and how I'd do it based on my experience with remote desktop apps.
Coming to how they're different, I think the biggest distinctions are how I've chosen to handle Mac windows, the limited screen space on phones, and the overall UX.
Sill's optional virtual display moves the selected window onto a separate display sized for the receiver, which can resize the actual Mac window. MeowDisplay's Window view keeps the Mac window's existing size and position, adapting how it's displayed on the phone instead.
My reasoning behind this is that most desktop apps weren't designed for phone-sized windows. Resizing them can make their interfaces cramped or awkward, and I'd rather preserve their original layouts, even if that means occasionally zooming, which I find acceptable.
Sill currently focuses on displaying one window or the desktop at a time, while MeowDisplay offers a different multitasking workflow with multiple windows arranged in tabs and panes, and floating windows coming in 2.1.
Another difference is the screen space. Sill's portrait layout has the streamed picture at the top with a dedicated trackpad below it, although it also offers a Larger Picture option and direct touch.
I've questioned why we even need a separate trackpad when the whole phone is already a touch surface. MeowDisplay lets you use the displayed content itself for Direct Touch or trackpad-style input, without sacrificing a portion of the screen for a dedicated trackpad. Personally, I find that screen space too valuable to give up.
There's a difference in how you navigate through the UI as well. Sill has window thumbnails and app selection, while MeowDisplay uses Stage Peek, which you pull from the screen's edge to browse and search windows and apps, along with an expanded window overview.
So yupp, we're both trying to solve a similar problem, just with different approaches and trade-offs. I think some people might prefer Sill's approach, and others might prefer MeowDisplay's.
This seems more relevant than ever in days that we're sending off an LLM prompt and then letting it chug away for who knows how long. I tend to just leave my screen on with the mouse in a hotcorner that disables the screensaver.
Al Dente.app has you covered.
It doesn't work for a fully shut-down Mac though, and remote waking over something like Tailscale isn't supported yet. That would need something already awake on the Mac's local network, like a compatible router or another device, to relay the wake request. I've been looking into that.
As for keeping it awake, macOS already lets you prevent automatic sleep whilst you're plugged into power, even with the display turned off, so you wouldn't need to leave the screen running all the time.
EDIT: Yes, the feature is called Sidecar.
I've considered supporting macOS's built-in Screen Sharing too, though with fewer features.