Earlier quoted context omitted.
I think Telegram uses Qt.
Yep, Telegram on Desktop uses Qt. It's even open-source and on GitHub: https://github.com/telegramdesktop/tdesktop
Going native
171–180 of 245 posts
Re: Going native
#172Earlier quoted context omitted.
Why not call it "standalone app" (Chrome-less! though that might be confusing for other reasons.)
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
#173I love postman. The whole program is extremely well designed, and the dark theme looks fantastic. Might even be better than Darcula on intelliJ :p Since the author is in the comments just wanted to ask one thing. Is this [1] supposed to be misaligned? [1] https://i.imgur.com/aw8ybBz.png
Re: Going native
#174Re: Going native
#175Earlier quoted context omitted.
Main page scroll down, "A powerful GUI platform to make your API development faster & easier, from building API requests through testing, documentation and sharing."
So this is a text editor?
You are saying... "A powerful GUI platform to make your API development faster & easier, from building API requests through testing, documentation and sharing." makes you think a text editor, really?
Re: Going native
#176When 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…
There's already too many of them, and some hardware doesn't like having too many chrome instances running at once.
My PC is an i7 with 4 hyper-threaded cores, and an Nvidia Quadro 2000M. I usually have running, as far as electron goes: Chrome, Discord, remote-working app.
As soon as i add another electron app to the mix the hardware interrupt activity of my machine goes out of control, presumably because too many chrome instances are trying to share the same device for hardware acceleration.
This never happens with non-electron software.
Re: Going native
#177My 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.
Re: Going native
#178Earlier 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.
Re: Going native
#179These '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.
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.
Re: Going native
#180Postman 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…
From https://www.getpostman.com/
"A powerful GUI platform to make your API development faster & easier, from building API requests through testing, documentation and sharing"
Then searching, I found this:
https://seesparkbox.com/foundry/api_testing_with_postman
"...for interacting with HTTP APIs. It presents you with a friendly GUI for constructing requests and reading responses"
It's a bit sad I (an experienced dev) need to google outside your site to find out what your product does. Hope this helps.