> Yeah the problem is having to write 5 apps, not the inconsistency.

Isn’t that what abstraction and interface is about? You can write the common business logic and presentation concerns, and then share it across each native implementation.

That is what web wrapping is in truth, but it’s just inneficient because of the huge surface area of web technologies.

▲

mort96 5 hours ago | parent [-]

For a whole lot of apps, almost all of the difficult stuff is in making the UI feel right.

▲

skydhash 5 hours ago | parent [-]

Aesthetics, usability, and technical flavor are different axes and feel right is a subjective point. And based on anecdata, usability is what actual users want. Web wrapping is mostly an exclusive focus on aesthetics. With native frameworks, you often get very close to "feel right" without much effort.

	▲	Karrot_Kream 3 hours ago \| parent [-]
		> With native frameworks, you often get very close to "feel right" without much effort. I've only seen this sentiment on nerd forums but never among my less technical friends, so I'm a bit reluctant to accept this wisdom honestly. That said, if you're just building something for a technical crowd you'll probably make them much happier if you make your implementation use native widgets and take up much less memory and redraw faster at the expense of a slightly jankier UX. Though, this is probably why IRC clients all feel janky lol. For example a lot of my less technical friends/family really like the visual design of Spotify even though it conflicts with a lot of design language on MacOS, Windows, and Android.