Web vs Native UIs

The cluster centers on debates comparing web-based UI development (HTML/CSS/React) to native toolkits like Qt, GTK, and Cocoa, criticizing web's limitations for complex interfaces and praising native tooling, declarative approaches, and visual builders.

📉 Falling 0.4x Web Development
4,849
Comments
20
Years Active
5
Top Authors
#4047
Topic ID

Activity Over Time

2007
6
2008
43
2009
89
2010
116
2011
165
2012
132
2013
186
2014
210
2015
196
2016
226
2017
362
2018
317
2019
374
2020
391
2021
346
2022
451
2023
477
2024
393
2025
337
2026
32

Keywords

QT IMHO DevTools AppKit IDE GWT UI AWT WPF OO ui uis widget html web layout gui frameworks code design

Sample Comments

Filligree Jul 9, 2022 View on HN

Not with the current state of the UI frameworks, not really.

dmitriid Feb 12, 2020 View on HN

You're confusing the technology to create UI with the UI itself.

baybal2 Feb 13, 2020 View on HN

Web is very inferior to any modestly well done UI toolkit.

neop1x Aug 6, 2020 View on HN

Yes, at the end of the day, one can see why there are UI frameworks like Qt, GTK, Cocoa. It took many, many, many years and people to develop them and they are designed for complex desktop interfaces.I don't like this constant reinvention of wheels. Look at Blender, it also has its own, mice UI and many other specialized graphical, image and audio apps have. Flutter also renders its widgets.But none of them is as universal and flexible as those big, battle-tested frameworks.They are n

btbuildem Jan 5, 2022 View on HN

What is the advantage? Does it make some things easier that are very hard to do in languages / frameworks traditionally used to build app/webapp GUIs?

flatline Dec 9, 2023 View on HN

I worked with a non-software team that used this to build a UI about two years ago. It’s great to spin up something quickly, and worked well for a team that didn’t have much UI experience - to a point. It becomes very hard to maintain and navigate as soon as any complexity comes in - much harder than Qt, Winforms, or Swing. The styling was lackluster. Maybe it’s improved in that time, but I think its place is quick one-off UIs and rapid prototyping.

drdaeman Jul 27, 2017 View on HN

I think it's also about the tooling.With most "native" platforms you can have a WYSIWYG UI editing (because those markup languages were designed with that in mind). You visually define the layout (with mouse/trackpad), drop components there, and it's all nice and easy to use. Surely, you can code your UI as well, but to best of my knowledge no one in their sane mind does this, unless they have some very good reasons.With web apps (progressive or not), the usual app

crummy Aug 18, 2022 View on HN

what languages are known for convenient UI development?

digi_owl Feb 6, 2017 View on HN

Why do we keep trying to make web sites into a UI toolkit?!

iddan May 22, 2021 View on HN

I think UI builders are considered as good tools, it’s the XML that is “not needed”