Live data from Hacker News

Goodbye, Native Apps

medium.com

171–180 of 231 posts

Re: Goodbye, Native Apps

#171

Paw is a far better app than Postman, on a Mac, for no other reason than it is native and behaves as you would expect.

Last time i checked this app felt native https://hoppscotch.io/

(See the fact that you can use it after a click, how can i do the same with paw ?)

Re: Goodbye, Native Apps

#172

Earlier quoted context omitted.

I keep hearing the "web technologies are fine, you're just using them wrong" refrain over and over again, but it's ultimately not very convincing. If it's true, then where are all the good web applications? I've certainly never seen any of them. Can you give an example? If nobody can get Web technologies to deliver a good experience, then I'm not sure it matters that much whether or not it's possible in theory. Deliv…

What do you consider a good application? If you have never seen anything that would qualify on the Web then I have to ask what standards you are seeking and whether any software actually meets them.

At least for the purposes of comparing to web apps, the criteria would be: responsive/low-latency (responds to input quickly), fast (completes tasks quickly), uses resources proportional to the functionality it provides, and doesn't often hang or spend noticeable amounts of time waiting for a network request before responding to an action.

Applications that meet these criteria include: Thunderbird, KiCAD, VLC, Vim, tmux, Blender, evince, Handbrake, and Pidgin.

Re: Goodbye, Native Apps

#173

How is this getting uovoted ? Is nobody reading the article ? A few paragraphs in and I can see the author has terrible writing skills and doesn't know what he's talking about >In fact, writing software with C/C++ was hard because developers had to work with different operating system API(Application Programming Interface). Seriously ? Writing C++ apps is hard because you had to use different APIs ? That's the least…

This should tell you something about the quality of patrons on this site.

Re: Goodbye, Native Apps

#174
post #108

Earlier quoted context omitted.

While there are really good looking examples to me the most of web apps do not look slick at all. They're rather extremely unergonomic

I don't disagree, but I think you could say the same about native apps too. For this discussion, I think the most important thing is what good examples of each type can achieve, since presumably those are the ones that most people will choose to use.

>"I don't disagree, but I think you could say the same about native apps too"

Of course I could. I was just countering the original point that sounded that web apps are slick just because they're web apps. Making good GUI is hard (well I'd skip Hello world here).

Re: Goodbye, Native Apps

#175
I know the article is talking about "truly" native apps, but React Native is quite an interesting project. Microsoft has been heavily investing into React Native for Windows and macOS, so combined with RNWeb (which is still a work in progress, but quite usable), a developer can target iOS, Android, Windows, macOS and web with the same code base and have a native UI for each platform. It's pretty magical when it all works.

Re: Goodbye, Native Apps

#176

Paw is a far better app than Postman, on a Mac, for no other reason than it is native and behaves as you would expect.

Last time i checked this app felt native https://hoppscotch.io/ (See the fact that you can use it after a click, how can i do the same with paw ?)

It feels like a browser app. It’s snappy, but not as snappy as native.

You also need to expend several more clicks to install a browser extension to get the same level of functionality that Paw has.

Re: Goodbye, Native Apps

#177
post #131

Earlier quoted context omitted.

> Windows Forms will work for forever but hasn't been touched in a long time WinForms very recently got HiDPI support, better accessibility features, and was ported to .NET Core where they also fixed bugs in some controls. WPF in the meantime has been arbitrarily declared stable and Microsoft refuses to fix anything. Everybody is supposed to switch to UWP which they already deprecated or WinUI which hasn't been relea…

Windows Forms remains supported, yeah, but there are no marquee feature to make it easier to develop for really. That seems like it's more focused on getting people to bring their existing WinForms work to .NET Core.

They complete revamped the WinForms designer for .NET 5 in Visual Studio 2019. It's buggy as hell (as is the rest von VS2019) but they tried to make it better and are definitely not doing nothing.

Re: Goodbye, Native Apps

#178

Earlier quoted context omitted.

Indeed, my prediction is that native apps will make a comeback when the UI toolkits catch up. Flutter is in this vein. And some of the Rust UI ecosystem looks promising (although very early stage).

Can they catch up? I feel the reason why web apps took off is because so much money has been spent on the underlying technologies (HTML, CSS, etc.) that makes them extremely powerful. I’ve used a lot of UI frameworks and getting to do anything complex is always much harder than doing the equivalent in HTML/CSS/etc.

I think so. Web has the advantage of already catering to literally every layout & style use case (grid, multiple columns, floats, inline elements, etc. etc. etc.). But Flutter has the advantage of being designed from scratch so it can avoid all the idiotic mistakes the CSS made (e.g. box-sizing, the insane difficulty of centering things, etc.).

I don't think it will take too long for the niceness of a sane design to outweigh the lack of features.

The only thing I'm not convinced about is that Flutter-web will ever be viable for most web pages (i.e. non-app ones). It kind of works but it's big and slow. Probably eventually people will do a native website, and then use Flutter for mobile and desktop.

Re: Goodbye, Native Apps

#179

As much as anything else the growth of hybrid apps is a symptom of a couple of things: 1) people now expect apps to run on a million different devices and nobody has the time or resources to develop four or five native apps with feature parity between them 2) progress on UI frameworks is pretty much stalled. Just looking at .NET, because I'm familiar with it and traditionally desktop software has been a big area of c…

If you take a look at the GTK+ ecosystem...it's kinda broken, too. Simple use case: Make a sidebar fade in and fade out, while changing the dimensions of the right box. Pretty close to impossible to implement in a clean manner, even within glade. And then, try to support a mobile device in a responsive way with libhandy. Now you throw the towel and just get on with 20 lines of CSS and literally two HTML elements. CSS…

I never coded GTK apps, but isn't the theming done with CSS since GTK 3?

Re: Goodbye, Native Apps

#180

How is this getting uovoted ? Is nobody reading the article ? A few paragraphs in and I can see the author has terrible writing skills and doesn't know what he's talking about >In fact, writing software with C/C++ was hard because developers had to work with different operating system API(Application Programming Interface). Seriously ? Writing C++ apps is hard because you had to use different APIs ? That's the least…

My thoughts exactly. The one problem with native apps is the resources and time you need to develop the same app for several platforms. That's all.

That seems to me to be what the Medium author was saying.
Post reply on HN