5 ms·
HN, GitHub and other such sites heavily skew towards developers who can tell, yes. I am talking about the vast majority of people who, I guarantee you, would no
by satvikpendem 3y ago
HN, GitHub and other such sites heavily skew towards developers who can tell, yes. I am talking about the vast majority of people who, I guarantee you, would not be able to tell a native component from a non-native one. The teams I have been on have done user testing for precisely this, comparing native vs cross platform frameworks as we were evaluating whether to use them or not. Literally 99% of the people we talked to did not notice or care, which actually falls in line quite nicely to how much of the US population are software engineers, ~1%.
If you doubt my results, talk to your non-technical friends and show them apps that are native vs those that aren't and hear what they say.
- inferiorhuman 3y agoLiterally 99% of the people we talked to did not notice or care Or they've decided there are better things to do than try to convince someone who's got a vested interest in defending their current tech stack. The text rendering problems with e.g. Github are something even a blind person could see – yet you're dismissing them as highly arcane things that only a developer would notice. Actually, a blind person would also likely notice your non-native app because it almost certainly doesn't integrate well (if at all) with operating system accessibility features.
- satvikpendem 3y agoWe didn't have a "vested interest" in any tech stack, this was all preliminary testing before we built out anything. If you want to take any evidence of what people empirically care about as being somehow a bias or flaw in testing methodology on our part, then do your own user testing and likely come to the same conclusions as us. You've reduced the problem from something apparently everyone can readily see to now the blind (again, blind who? Blind developers). Accessibility is important which is why every cross platform framework of note has accessibility solutions, the web is not the only user interface that implements accessibility. This says nothing about how much people who are able-bodied care, which, again, is the vast majority of people who simply do not care. Just because one observes some problem to exist does not mean that everyone else feels the same, however much one would like to be vindicated of their experience of the problem.
- inferiorhuman 3y agoYou've reduced the problem from something apparently everyone can readily see And you've dismissed this as something only a developer would notice: https://user-images.githubusercontent.com/1002257/248511013-989438c8-92e1-4888-b3bc-556192726429.png https://user-images.githubusercontent.com/1002257/248511013-... https://user-images.githubusercontent.com/440661/246317472-af1d648b-60db-4e08-b807-908aafd7c69e.png https://user-images.githubusercontent.com/440661/246317472-a... https://user-images.githubusercontent.com/128169473/239261154-ee660182-ba86-4ce7-bfd8-5d87378d17f8.png https://user-images.githubusercontent.com/128169473/23926115... You're greatly overestimating how willing people are to take the effort to complain. At the end of the day non-native toolkits have lowered folks expectations to the point that (save for the occasional "why are computers so fast and apps so slow" comments) they're quite likely to accept a low quality app. If you've got 99% of any group agreeing on anything subjective there's a problem with your measurement.
- satvikpendem 3y agoSure, that's an egregious example, maybe GitHub did mess up, I won't deny that, but that one example is not indicative of the entire class of cross platform frameworks being useless. > If you've got 99% of any group agreeing on anything subjective there's a problem with your measurement. Okay, do your own testing and measure it however you want, then get back to me about methodological errors. Because as far as we can tell, most users do not care. In fact, we received messages about how happy they are with the apps and how slick the UX and UI are. You can make good and bad apps in any framework.
- splintercell 3y agoI have never seen this problem on GitHub, which platform does this happen in?
- fauigerzigerk 3y agoPeople care about battery drain: https://github.com/flutter/flutter/issues/59327 https://github.com/flutter/flutter/issues/59327 I have turned pessimistic on Flutter after they failed to fix this catastrophic issue for years, and I'm not someone who is ideologically opposed to cross-platform UI technologies in general. Imitating native user interfaces takes a huge and continued effort. It's always a step behind and in danger of falling further behind. How long until it gets defunded?
- satvikpendem 3y agoIt does suck that Flutter doesn't have as much bandwidth for people working on it as I'd like, but I'm not sure there's much one can do short of directly contributing and sending PRs, which it seems the author of that issue has done for a temporary fix.
- fauigerzigerk 3y agoThe "temporary" fix is to allow developers to disable the cursor animation, i.e deviate from the native look & feel. After almost four years of saddling every Flutter app that uses text input with anywhere between 5% and 20% CPU usage, this is what they have come up with. What this tells me is that it is neither possible nor beneficial to imitate native UI toolkits using a completely different technology stack. It's simply the wrong architecture.
- satvikpendem 3y agoWell, I guess there's no free lunch after all. At least it's better than Electron in that it's compiled code, and that it works on 6 different OSes.
- fauigerzigerk 3y agoI disagree. Web technologies are highly optimised for what they do (i.e text field uses 0% of CPU), run compiled code on all platforms and don't waste resources on chasing this unachievable and pointless native fetish. I don't understand your position. You're saying (correctly I think) that most users don't care about native. But then you turn around and choose an immature technology that spends a significant share of its budget on trying and failing to imitate native. The bug I cited betrays the priorities of the project. They chose to prioritise chasing "native" over fixing a critical bug for many years. Also, look at the large amount of investment going into web technologies - WebAssembly, WebGPU and many others. Even much criticised Apple is putting in a lot of work. I don't think the completely isolated Flutter/Dart team will ever be able to compete.