News for hackers. Stuff that matters.
Re:Going native by psyklic on Thursday March 23, 2017 @10:30PM (#13946126)
>> 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 by arithma on Friday March 24, 2017 @04:05AM (#13947404)
Why not call it "standalone app" (Chrome-less! though that might be confusing for other reasons.)
Re:Going native by lloeki on Friday March 24, 2017 @04:22AM (#13947460)
Mattermost (and Telegram?) call the electron-based apps "desktop apps", which is I feel is a nice tradeoff: not native but not browser.
Re:Going native by garaetjjte on Friday March 24, 2017 @04:55AM (#13947562)
I think Telegram uses Qt.
Re:Going native by KuiN on Friday March 24, 2017 @05:33AM (#13947695)
Yep, Telegram on Desktop uses Qt. It's even open-source and on GitHub: https://github.com/telegramdesktop/tdesktop
Re:Going native by rvanmil on Friday March 24, 2017 @06:43AM (#13947987)
There's a separate macOS version as well: https://github.com/overtake/telegram
Re:Going native by lloeki on Friday March 24, 2017 @05:37AM (#13947706)
They used to have two apps, one using Cocoa (named "Telegram") and the other Electron (named "Telegram Desktop"). They transitioned the Electron app to QT and kept the "Telegram Desktop" name.
Re:Going native by Mithaldu on Friday March 24, 2017 @06:55AM (#13948035)
Electron is a browser though, just one with a lot of the chrome cut out.
Re:Going native by TeMPOraL on Friday March 24, 2017 @07:04AM (#13948075)
Chrome without the chrome.
Re:Going native by a85 on Friday March 24, 2017 @10:46AM (#13949208)
Naming things is tricky. Postman exists in the following places:

1. In-browser Chrome extension with a UI (Postman legacy app)

2. In-browser Chrome extension without a UI (Postman Interceptor)

3. Stand-alone/desktop Chrome app (can be run withput Chrome)

4. Command line tool (newman - runs the same runtime as Postman)

5. Stand-alone/native apps that can be installed (where most of the debate on this thread is)

6. Server-side runtime

We chose to use "native" because it avoids the confusion with the existing Chrome desktop app and informs people about the advantages of this version v/s the previous version in one word.

Re:Going native by Ajedi32 on Friday March 24, 2017 @09:49AM (#13948867)
I think the line's a lot more blurry than you make it out to be.

Not only are Electron apps often visually and functionally indistinguishable from "native" applications on their respective platforms, but there are also varying degrees of integration with the underlying platform you can have within Electron apps.

For example, Electron supports including native modules which have to be compiled for a specific platform. How many of those would an Electron app have to use before it's considered "native"? Or what about an app like Spotify, which only uses a web view for certain components of the UI and everything else is written in C/C++? Does merely using an interpreted language like JS or Python anywhere in your app mean it's no longer native?

Also, keep in mind that this blog post was written for Postman's users, it's not a technical write up. Postman's users may be more technical than most, but they still shouldn't have to know or care what underlying technology was used to build Postman's desktop apps. From their perspective calling them "native" apps is perfectly accurate, as they behave as native apps in every respect.

Re:Going native by swiley on Friday March 24, 2017 @10:15AM (#13949009)
Electron apps are most certainly not functionally indistinguishable from native apps. They are always much larger and always seem to consume orders of magnitude more resources (memory, CPU.) If despotify still worked I would absolutely use that instead of the slow, buggy webview based official client.

People want native apps because they don't want the cooling/memory/power consumption from the web, as well as their delay tolerance and consistent UI. Electron can only provide the second (and sometimes the third.)

Re:Going native by Ajedi32 on Friday March 24, 2017 @11:53AM (#13949740)
Performance is a property of an application as a whole, not just the framework it's built on.

While you can certainly argue that apps which use webviews are slower on average than their native counterparts; Electron-based apps aren't necessarily always going to be slow; and native apps aren't necessarily always going to be fast.

Therefore, since a user cannot conclude that an app is "not native" merely by observing its performance, Electron apps cannot be said to be functionally distinguishable from native apps merely because they're slower, on average, than other applications.

Re:Going native by debaserab2 on Friday March 24, 2017 @01:07PM (#13950422)
People conclude things based on their experience using them. There are a lot of bloated feeling electron apps out there that are popular right now, which leads to people concluding (not incorrectly) that electron apps tend to be slower than native ones based on their experience.
Re:Going native by a85 on Friday March 24, 2017 @01:40PM (#13950690)
Agreed. However, perceptions change as technology improves and overall the arc of software tools has been towards higher level abstractions unless absolutely required to go deeper.
Re:Going native by a85 on Friday March 24, 2017 @10:44AM (#13949192)
That's a valid concern and I believe all developers who are working on the platform will address this. If memory/power consumption on laptops was so draining just because something was in HTML/CSS/JS, I believe people would have stopped using browsers or probably just stuck to 1-tab per browser.
Re:Going native by alok-g on Saturday March 25, 2017 @05:43AM (#13954786)
>> The term "native" is used to describe apps developed for a specific operating system.

I would have said that "native" means compiled for a specific operating system or a processor. If someone develops an app using Qt which then works on multiple operating systems, it would still be considered native.

Re:Going native by alnitak on Friday March 24, 2017 @01:00AM (#13946719)
The pedantic force is strong here.
Re:Going native by debaserab2 on Friday March 24, 2017 @01:18AM (#13946808)
Not really. Especially not on Hacker News. There's an expectation when someone says native app that you're getting a binary that you compiled from source you created with a reasonable expectation of performance.

No one thinks native as being a webview wrapped executable where the authored source is actually a series of HTML, CSS, and javascript. They just don't. Calling it "native" is a misnomer.

Re:Going native by wging on Friday March 24, 2017 @01:27AM (#13946843)
You're right about the meaning of 'native', but if you expect to have a 'reasonable expectation of performance' just because an app is written as a native binary, you may be sorely disappointed. There are plenty of poorly performing native applications out there, and it's also certainly possible to write minimal, fast HTML/CSS/JavaScript.
Re:Going native by debaserab2 on Friday March 24, 2017 @01:47AM (#13946943)
Absolutely. But you don't start out with a large memory footprint like an electron app, you actually have to code yourself into that problem instead of immediately inheriting it.

I'd still argue that most people are going to assume that a native app is probably faster than your average electron app, for a whole host of reasons.

Re:Going native by jorvi on Friday March 24, 2017 @01:55AM (#13946986)
That's comparing outlier to outlier. If you compare two averagely coded apps, something written in C++ will make an absolute joke of something written in Javascript.
Re:Going native by a85 on Friday March 24, 2017 @11:09AM (#13949386)
What if the application does have compiled libraries generated from the authored source?
Re:Going native by debaserab2 on Friday March 24, 2017 @01:10PM (#13950441)
I'm not trying to define what a native app is, I'm only explaining the way many users such as myself perceive it today. The waters are obviously getting much murkier on what fits the definition of native and it does look like the writing is on the wall that the state javascript on the desktop is just going to continue to improve.
Re:Going native by batmansmk on Friday March 24, 2017 @02:46AM (#13947153)
What about using electron with the cachedData option...? Or some webassembly thrown into the mix? Is native a development style or a product?
Re:Going native by Qwertious on Friday March 24, 2017 @02:30AM (#13947092)
People who aren't pedantic in tech end up wasting thousands of dollars due to miscommunication.
Re:Going native by kwhitefoot on Friday March 24, 2017 @09:20AM (#13948699)
I wish I upvote this more than once.
Re:Going native by JustSomeNobody on Friday March 24, 2017 @07:54AM (#13948278)
Words have meaning.

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

Re:Going native by Touche on Friday March 24, 2017 @08:52AM (#13948541)
Words do have meaning but "native" has pretty unclear meaning.

Is JavaScript native? JavaScript is interpreted when it first starts, but eventually turns into machine code through JIT by most JS engines. So is JavaScript native because it gets converted to machine code, just as C++ does?

If you say no, then you're saying only AOT compiled languages are "native". So that eliminates Python, Erlang, Java. Even C#, the "native" language on Windows is not AOT (in most cases).

So that doesn't work, AOT has nothing to do with native. JavaScript is just as native as any other language.

So maybe the problem is the UI, right? That's where most people seem to have a problem. So as long as you are using Cocoa on OSX, GTK on Gnome, Metro on Windows, you're native, right? Oh, wait, Metro apps can be written using HTML, JS, and CSS. They are essentially identical to Electron apps. In fact, Microsoft supports (and encourages) you to create .appx packages from Electron apps [1].

Oh, and all of those Qt apps out there (like Calibre, by far the best ebook management software), not native (despite being C++ in a lot of cases).

So yeah, "native" has meaning, but the meaning is as clear as mud.

[1]https://github.com/felixrieseberg/electron-windows-store

Re:Going native by logicallee on Thursday March 30, 2017 @12:14AM (#13992837)
Just commenting that that is a very good definition of what realtime isn't! :)
Re:Going native by shamasis on Friday March 24, 2017 @01:07AM (#13946753)
Ah! 15 years back I knew APIs were those Win32 ones listed by Microsoft to access insides of Windows.

Things change.