Read the article, went to home page, clicked in Documentation and still don't know what the application does. Can someone resume in 2 phrases?
Going native
91–100 of 245 posts
Re: Going native
#92Read the article, went to home page, clicked in Documentation and still don't know what the application does. Can someone resume in 2 phrases?
Basically, it's a program for running tests against an API (HTTP VERBS).
Re: Going native
#93Big fan of Postman for quickly iterating on API's, microservice integration tests, and one off requests. However, my team keeps the collections in git and they are very difficult to diff. This almost always require a detailed commit (doesnt usually happen) or me asking the dev what they changed. Any suggestions on how to improve comparing two collections?
Re: Going native
#94When did we start calling Electron Apps, Native Apps? Is it now a marketing ploy to call your App native when it's not? If your App renders in a WebView then by definition it's not native and shouldn't be labelled as such so it doesn't devalue Apps that use Native OS's UI components and idioms that are truly Native. If it has a mix of native and WebView controls then it's at best a Hybrid App.
I am not sure why something would be inherently superior if it is using pre-built OS components. Any software can have memory leaks, buggy behavior, weird input issues etc. I'd rather look at the user experience and qualify something as better/worse after using it. Postman had issues in the beginning when we started porting things over but these were quickly solved and in fact gave us much more power over the experie…
Even if it's not superior, this is still false advertising.
But, embedding the app in a browser always adds bloat - there's no way around that. It may not be obvious in case of huge apps, but there are many examples of trivial things shipped with electron - which make a simple single-dialog box app a 300MB monster.
Re: Going native
#95Postman founder here HN folks. Great to see the post get featured on the homepage! Lots of discussion about what is exactly native. I have posted some replies but some other points about the choice of words: 1. Postman has 3 million users and about 1.5 million MAUs. When we tell people we have a native app, they get it. People go to our apps page, download the installer and see everything exactly as they expect thing…
>> When we tell people we have a native app, they get it. People go to our apps page, download the installer and see everything exactly as they expect things to be.
The term "native" is used to describe apps developed for a specific operating system. By this definition, clearly Electron apps (and hence Postman) are not native apps.
Having to download an installer doesn't make it native. On smartphones, all apps are installed in the same way. Yet, some are native and others use WebViews.
I am making no comment on Postman's quality (in fact I am a customer). However, advertising Postman as native seems a bit disconcerting to me.
Re: Going native
#96When did we start calling Electron Apps, Native Apps? Is it now a marketing ploy to call your App native when it's not? If your App renders in a WebView then by definition it's not native and shouldn't be labelled as such so it doesn't devalue Apps that use Native OS's UI components and idioms that are truly Native. If it has a mix of native and WebView controls then it's at best a Hybrid App.
In the case of this specific post, they seem to be using "native" to mean "has features that require access to native OS APIs, and which cannot exist purely within the HTML5 abstract machine." There's probably a better term for this. "Native-enabled", perhaps? "Unsandboxed"?
Sandbox is a completely different idea. Both native and web apps can have sandboxes (or not have them).
Re: Going native
#97I think it's really disappointing that so many of the commenters here have chosen to nitpick on the author's choice of the word native and then debating whether it was a good idea for them to use Electron. How about we all try out the app for a few days and the come report back about our experience?
Re: Going native
#98I'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.
I really like this feature too
Re: Going native
#99Postman founder here HN folks. Great to see the post get featured on the homepage! Lots of discussion about what is exactly native. I have posted some replies but some other points about the choice of words: 1. Postman has 3 million users and about 1.5 million MAUs. When we tell people we have a native app, they get it. People go to our apps page, download the installer and see everything exactly as they expect thing…
> When we tell people we have a native app, they get it.
Are people here not... people? You seem to describe a desktop app. Bring able to install it has nothing to do with being native or not.
Re: Going native
#100Thank goodness. The biggest problem with the chrome app is that alt+tabbing to Chrome will foreground Postman instead. Such a pain!
Yeah, it was a constant dance of `cmd-tab` and `cmd-tilde` on OSX, which unfortunately was the reason I lost interest in it.