Going native • Hacker News Board

Re: Going native

#21

Post by a85 » Thu, Mar 23, 2017, 11:08 PM UTC

aberatiu wrote: post #7

My 2 cents. Try and add a notification within your Chrome App that there's a native version of your app as well. 'Cuz since now, although I've been using your app for more than a year now, I didn't know about the native version of the app. PS: Paying customer :)

Yep. :) Up next. (Postman founder here)

Re: Going native

#22

Post by CountSessine » Thu, Mar 23, 2017, 11:09 PM UTC

johnflan wrote: post #12

These 'native' wrapped apps on desktop and mobile are always less in some way than a real native app. I know there is a cost benefit argument, but I personally avoid them.

I don't think that that's always true. I think the gold-standard for this is Slack (at least on OSX). Spotify is nice too. Both seem to combine the very best of web dev (nice presentation and service integration) while cancelling out its worst problems (like accidental browser navigation).

Re: Going native

#23

Post by a85 » Thu, Mar 23, 2017, 11:10 PM UTC

eyko wrote: post #16

EduardoBautista wrote: post #4

Earlier quoted context omitted.

Yup. Luckily, there is Paw[0] if you want a native experience on the mac. [0]: https://paw.cloud

I liked paw, but postman is free. I'd consider paw at half the price because I don't spend that much time testing REST APIs, but when I do I don't mind using a better tool than httpie or curl. Postman does the job (quite well) for free.

We do have a subscription service now called Postman Pro - does API documentation (api.getpostman.com), API Monitoring, Mock servers, Team collaboration and it has a powerful API (api.getpostman.com). More coming soon! Postman - the app will always remain free. :) (Founder here)

Re: Going native

#24

Post by jsmeaton » Thu, Mar 23, 2017, 11:11 PM UTC

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.

Re: Going native

#25

Post by jitix » Thu, Mar 23, 2017, 11:12 PM UTC

This is a great news. I was looking for a decent, free ReST client for Mac for a long time.

Re: Going native

#26

Post by fimdomeio » Thu, Mar 23, 2017, 11:12 PM UTC

juice_bus wrote: post #6

I am really getting tired of the constant "need an account" for _everything_ - nvidia being the one that drives me the most crazy. I appreciate the fact that Postman allows you to continue without registration[0] [0] http://i.imgur.com/8XVCu5u.png

What I would love would be a git friendly app. keep the collection as a file that I can keep on the repo and them commit the new changes in the code.

Re: Going native

#27

Post by elmalto » Thu, Mar 23, 2017, 11:12 PM UTC

Gladly switched today after the plugin, although installed in "normal" Chrome, opened up Canary every time I used it.

Re: Going native

#28

Post by ozten » Thu, Mar 23, 2017, 11:13 PM UTC

tbrock wrote: post #5

The 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.

Re: Going native

#29

Post by a85 » Thu, Mar 23, 2017, 11:13 PM UTC

johnflan wrote: post #12

These 'native' wrapped apps on desktop and mobile are always less in some way than a real native app. I know there is a cost benefit argument, but I personally avoid them.

I'd argue that the HTML/CSS/JS layer is more powerful and more extensible than any native rendering layer.

We are building some awesome UI components using this: http://blog.getpostman.com/2017/02/28/introducing-the-new-da...

Things that we build for the app are also available for our web components instantly. React makes this even easier.

Re: Going native

#30

Post by paulddraper » Thu, Mar 23, 2017, 11:14 PM UTC

a85 wrote: post #17

macsj200 wrote: post #2

"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…

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.