Going native • Hacker News Board

Re: Going native

#241

Post by martin-adams » Sat, Mar 25, 2017, 12:49 PM UTC

a85 wrote: post #212

martin-adams wrote: post #177

I absolutely love the Postman app, well done and thank you! My biggest frustration with native apps are things like the Google login. Without it being in a browser, I have no way to verify that I'm looking at a legitimate login, or a fake one, right through to 2 factor authentication.

Thank you for the comment! I think there are ways to represent this better (just with a URL bar for example). Will look into it.

I'm not sure how easy that is to solve, because again, a rogue app could fake the URL bar. It's just the nature of desktop apps vs the browser as the browser is there the trust is. Maybe passing it to a browser for authentication is the only option.

Now I've been using Postman for many years, so I certainly trust the quality and intent of your work.

Re: Going native

#242

Post by Antrikshy » Sat, Mar 25, 2017, 10:46 PM UTC

Qwertious wrote: post #144

colordrops wrote: post #39

Earlier quoted context omitted.

It's a native binary executable with standard access to system APIs, so in the technical sense, yes.

By that logic, if I fork chromium and make a custom version of it that's hard-coded to start up HN in the first tab, then I've made a native HN app.

But you won't have access to the file system unless you further modify it.

Re: Going native

#243

Post by wishinghand » Mon, Mar 27, 2017, 3:24 PM UTC

a85 wrote: post #239

dkersten wrote: post #220

Earlier quoted context omitted.

It depends on the host platform. On desktop, all native apps are desktop apps but not all desktop apps are native. On mobile, all native apps are mobile apps but not all mobile apps are native.

This is where I believe we'd differ. Postman already had a "desktop" app in the sense that Chrome apps also existed as desktop apps and when we ask users to switch, they wouldn't. For most users, desktop apps = things that run on the desktop. https://dcrazed.com/google-chrome-desktop-apps/

What you say you differ on doesn't seem to be incompatible with my assertion.

Re: Going native

#244

Post by statictype » Mon, Mar 27, 2017, 5:36 PM UTC

mittsh wrote: post #179

statictype wrote: post #58

Earlier quoted context omitted.

On the other hand, there's Paw, a delightful native app in the same category that has morphed into an unusable tool that hangs every few minutes. Native experiences aren't always better.

Paw founder here. I'm very sorry to hear this. If you don't mind, I'd love to know more details on what's happening. The logs available in Paw menu > "Get Debug Info…" are very helpful. If you don't mind sending these details to support@paw.cloud, we'd be very grateful! Thx!

Hi- thanks for reaching out. Will send it across.

Paw's a great tool but I've had problems with version 3 that have made me want to open it less often.

I understand that not everyone seems to be having that issue.

Will email the logs and hope you can find something.

Re: Going native

#245

Post by logicallee » Thu, Mar 30, 2017, 4:14 AM UTC

JustSomeNobody wrote: post #183

alnitak wrote: post #124

Earlier quoted context omitted.

The pedantic force is strong here.

Words have meaning. Native doesn't mean browser in a window. Same as realtime doesn't mean "it'll get there faster. Maybe"

Just commenting that that is a very good definition of what realtime isn't! :)