It's free, and cross-platform. And the team sharing capabilities are cheaper than Paw's. It's odd that Paw seems to bill its single platform nature as a feature.
There's some great FOSS alternatives too!
Postman may or may not call it native, I did here, and then tried to clarify what I meant since I realised it's nativeness depended on context.
Packaged applications still work in ChromeOS but soon packaged apps are going away from Windows/OSX.
FWIW, I do use macOS, I just thought it was an odd 'feature', not least because it makes it unportable and contributes to lock-in.
When you have cross-platform software, even with a large dev team, there has to be huge compromises. For example, do menus go at the top (macOS) or do you have menus on each window (Windows)? Does Quit go under "File" (Windows) or under the app name's menu (macOS)? If you look at the Google apps on the iPhone, they originally looked like native iPhone apps, but since then Google apps look and work the same between OSes. This makes sense for a branding and development perspective. The few users who switch platforms for whatever reason are pleased, but for people who just use a Mac don't care about other platforms and want all their Mac software to look and work the same. Some people use Safari just because it's a native Mac app. Many people used Camino for that reason, too (Camino was a native Mac browser using Mozilla's Gecko engine developed between 2002-2012, first released a year before Safari).
As an extreme example, personally, I avoid almost all Java apps. Yes, they're cross platform, but they're ugly, slow, and usually integrate poorly with the rest of my system. JetBrains apps are the only exception that come to mind.
Just a cool feature I learnt recently.
Paw has a lot of power behind it, otherwise if you're just doing basic POST requests, stick to httpie. The code generators and extensions are nice. Easily switching between environments (e.g. dev, staging, prod). History of run requests. Tying values from other requests into other requests—e.g. get an auth token from a login request, and use that in a header in all other requests. I still only use a fairly basic amount of the features too. It's a very polished app, and the devs seem good too.