I'm a big fan of postman, and I've been using the native app for a few months. It's great for exploring apis then dumping the code into either curl or requests for Python.
Thanks for the comment! (Postman founder here)
Going native
31–40 of 245 posts
Re: Going native
#32Thank goodness. The biggest problem with the chrome app is that alt+tabbing to Chrome will foreground Postman instead. Such a pain!
Re: Going native
#33The real question is why Chrome will no longer allow Chrome apps?
My guess is they are doubling down on Progressive Web Apps. Many users don't understand the "browser is an app store" model. Making installing an "App" a seamless transition for websites you constantly use, seems like a UX improvement, if Progressive can deliver on it's vision.
Yeah. That plus I believe it became exponentially difficult for the Chrome team to deliver a set of APIs for apps to replicate native experiences. One example was the menu bar. Apparently it would have required rewriting parts of Chromium in a generic way so Chrome could have its own menu bar AND allow customizability for apps. I was tracking bugs on the Chromium tracker for a while but don't have these links handy at this moment.
Re: Going native
#34Earlier quoted context omitted.
It's not just an embedded instance of Chromium. There are APIs that bridge the gap with the operating system. One way to look at this is that the UI layer runs on HTML/CSS/Javascript. VS Code, Slack etc. are other common examples. [Electron APIs]: https://electron.atom.io/docs/api/
Right. It's Chromium + JS APIs + some packaging. E.g. an API to write a file.
That's a bit too simplistic of an explanation IMHO. It's a mashup of chromium and nodejs; the entry point is a nodejs app.
Re: Going native
#35"The native apps cover all the features and functionality of the Chrome app and Chrome extension together, and more. The native apps run on Electron overcoming a lot of the restrictions of the Chrome platform." My understanding was that Electron is just an embedded instance of Chromium, so I'm reading this sentence more like "The native apps run on [embedded Chromium] overcoming a lot of the restrictions of the [stan…
Yup. Luckily, there is Paw[0] if you want a native experience on the mac. [0]: https://paw.cloud
Paw looks like a really nice, slick, professional tool. I've been using Postman for years and really like it, and am used to it. I've yet to see a 'use case' where Paw can do something that Postman cannot, so I would appreciate it if anyone familiar with both tools can point out a value proposition for switching apps.
Re: Going native
#36Earlier quoted context omitted.
It's not just an embedded instance of Chromium. There are APIs that bridge the gap with the operating system. One way to look at this is that the UI layer runs on HTML/CSS/Javascript. VS Code, Slack etc. are other common examples. [Electron APIs]: https://electron.atom.io/docs/api/
Right. It's Chromium + JS APIs + some packaging. E.g. an API to write a file.
Window, Menus, clipboard, etc.. (not just being able to write to a file) https://electron.atom.io/docs/api/
Re: Going native
#37I didn't know Postman had a proxy. I was about to pay to use Charles proxy.
Re: Going native
#38Hmm, does Electron really == "native" ??
== yes but probably not ===
Re: Going native
#39Hmm, does Electron really == "native" ??
It's a native binary executable with standard access to system APIs, so in the technical sense, yes.