Only reasonable way is shared core with thin UI layer on top. For Rust there is Crux, don’t know for other languages. Everything else is just compromise, like all Flutter apps I know on iOS are just atrocious.
I like this approach, it's what I had in mind, but Crux doesn't seem to support desktop targets. I know on MacOS you can get nice looking apps with their native toolkit, on Linux you have GTK4 which can be decent looking, but not amazing, and on Windows, I truly don't know. Native apps on Windows look crap to me (without even mentioning the advanced fragmentation in UI toolkits in Windows). Maybe someone has some good examples for Windows and Linux, using native SDKs.
Only partially true: macOS is supported, and one can fall back to the web. But you're right in that native Windows and Linux are still missing.
> Linux
Problem with Linux of course is that it's almost as fragmented as Windows, with Qt and GTK being the main toolkits, but a dozen more if you ask the wrong people :D
I personally don't like GTK, to me it (well, mainly Gnome) looks and feels like trying to copy macOS without understanding what makes it great, but Qt is a toolkit I can get behind…
Apple had much longer support lifetimes for their products than all their competitors long before talk of mandatory minimums started to reach actual governments.
Well, except Google Maps nowadays sucks for everything but POI discovery, and even that is getting worse with reviews getting tinkered with more and more. Not to speak of the abomination Google calls an user interface.
Only reason to use Google nowadays for me is travel in countries where neither Apple nor OSM have good coverage.
> alternative AppView, but then if you are only on the alternative you are invisible to anyone who is only on Tangled
That’s misunderstanding the at protocol. There is a difference between a pds, where the data lives, and the appview. Tangled (the appview) happens to also provide a pds (they didn’t always do), but displays data which lives on other pds’s just as well.
Just because `jj` wraps around git doesn't mean it cannot have another backend. My comment doesn't imply that it only wraps around `git`. More importantly, the other backend which `jj` offers is (afaik) exclusively used at Google. Unless you are a Googler you will be using `jj` with `git`.
Also, the comment was aimed at a person who is obviously very invested in `git`. I was doing my best to offer them a description of `jj` they could swallow.
And I hate every one of those apps (well, back when I used Facebook, years ago, I did), because they’re just bad iOS citizens. I, as most iOS users do, don’t care what apps look on Android. For Android users, it’s the same with iOS. Making shitty cross platform apps is all about branding and saving some money for developers, nothing about the users.
It’s cool that you are a non-conformist badass but their wild popularity proves that a native app experience doesn’t matter.
What does “bad iOS citizen” even mean?
It’s not even about saving money for developers, it’s about the fact that your users expect a consistent experience.
Imagine if you watched an NFL game on NBC and the on-screen graphics were different if you were watching on a Samsung TV versus an LG TV. That’s the issue with native app UI elements (and it would quite literally be an issue with content apps on smart TV app platforms which are way more fragmented than iOS versus Android).
Your conclusion is false, as you’re mixing stuff that shouldn’t be mixed here:
1. Spotify, Uber etc are popular because of their product, not the pure quality of their apps. People use Uber because they want to cheaply get somewhere, and Spotify cause that’s there all their shared playlists are.
2. People buy whatever tv is on sale when their old one breaks, but the vast majority will stay with their phone platform, so couldn’t care less what their apps look on the other platforms out there.
So, native experience does matter, but obviously only as one of multiple deciding factors.
> What does “bad iOS citizen” even mean?
Doesn’t look like native apps, doesn’t feel like native apps (come on, most multi platform frameworks don’t even get the scrolling right, one of the most basic forms of interaction), doesn’t use all of the platforms features to their fullest, as applicable for the type of app.
What I meant to say in my original message is that if you are using system default-ish iOS UI styling, Liquid Glass is not optional decoration. If you have your entirely own UI and design system, sure you don't need it. But many of these Flutter apps or other such toolkits are using it to approximate system default UI except either without the Liquid Glass parts or with uncanny and incomplete approximations of it.
macOS is fine on all officially supported machines. Windows 11 is fine on high-end machines, and sucks on everything else. I have to use Windows 11 for work unfortunately, an almost bare install with just the two programs we use added, no background stuff or other extra resource hogs, and it just. sucks. shit!
You forget you’re a minority. Most users use one platform, or at most one work one private (probably with different software). So most software should be optimized for the platform, not consistency across them.
reply