411–420 of 453 posts
Earlier quoted context omitted.
Google home is my most-hated mobile app. It’s slow, janky, buggy, and has terrible UX.
Every action requires waiting. Its so frustrating. Open the app, spinner. Click themostat, spinner. Change the temperature, spinner. Its so frustrating. I use Home Assistant now as my primary home control app.
Earlier quoted context omitted.
> Flutter is the only realistic option for true cross platform UIs that run everywhere. I understand that argument but 100% disagree. The web is the cross platform that runs everywhere (as in in a browser or webview). True it has many issues and some forms of it (electron) are not ideal for some use case but I believe it’s a better platform than flutter in almost every way. You say “true” cross platform and could arg…
> The web is the cross platform that runs everywhere (as in in a browser or webview). I understand that argument but 100% disagree. Development is horrible, it's anything but standard, comes with a lot of baggage, the performance is atrocious. It doesn't even run anywhere, it runs in a browser. A huge, bloated, hungry browser. You say Electron is not ideal, I say it's the worst thing that had happened to desktop comp…
I am not saying that electron-based apps are generally good or efficient. Most of them are frustratingly slow and awkward. But this inefficiency rarely seems to be constrained by local resources: the apps often stand still, consuming barely any resources (CPU time, memory, etc.) and taking ages to load each page. At the same time you can often visit the same page in Chrome and it will load almost instantly.
It is frustrating and I have no idea what is going on, but it doesn't seem like upgrading the PC would solve the issue.
Earlier quoted context omitted.
who builds desktop applications anymore? it feels weird to say but i am starting to like them again after transitioning to basically 100% thin client/cloud services for the past 15 years.
What qualifies as a "desktop application" these days? Is it any application designed primarily to work on a laptop or desktop form factor? A web application like SketchUp would qualify. Is it an application whose code is only stored locally, even if they don't work well with a laptop/desktop form factor? Any number of native mobile apps would qualify. What about a PWA that is cached locally but initially loaded via a…
I also don't consider native phone/tablet apps to be desktop apps
Earlier quoted context omitted.
For what it's worth I'm an Ionic developer and I find the grand-parent's description pretty accurate. I do like Capacitor though, but I think that's mostly because I've had to deal with Cordova before.
Please pin point the relevant DX issues so that it can get recognition and get fixed
Every framework has bugs and feature requests that are fighting for resources. And the ones affecting you _always_ seem more important than the ones that don't.
That being said, the fact that memory leaks in widely used components (e.g.: `` [1]) go mostly unnoticed both by Ionic developers and by the community [2] just doesn't give me confidence in Ionic being a framework used to build quality apps.
[1] - https://github.com/ionic-team/ionic-framework/issues/19242#issuecomment-556182556
[2] - the issue linked above has 5 upvotes in 3 years and no one even bothered to report a separate issue for the memory leak in ``, which seems even more serious and the developers have been made aware of itI still can't find, in the docs, there is an open bug/feature request to NATIVELY copy/paste from web? Do they support copy / paste on the web app without using a special widget?
I'm not aware of any planned/possible way to do copy exactly as you would an HTML page with HTML tags, but there's a big project to make selection and copying much simpler and more powerful (design doc [1], in progress PR[2]). With that PR it should be easy to just add one SelectionArea to the root of your app in order to make everything selectable, like it would be on a web page. You don't need SelectableText widget…
Earlier quoted context omitted.
The answer to both of these things is the accessibility object model. You weren’t wrong historically but you aren’t right currently. Flutter web including the canvas rendering option has proper accessibility as of today AFAIK.
But you're still SOL if you want to use an ad blocker, right?
I was recently tasked to build a mobile app at my work, that would have maybe 5% of the feature-set of our gargantuan web product. However, this 5% was mission critical. Coming from React-TS, building with Flutter was a bit weird at first (where's my CSS???) but the productivity gains came quickly. The Pub ecosystem is fairly mature, in that all the third party packages are pretty high quality and address most common…
Earlier quoted context omitted.
Please pin point the relevant DX issues so that it can get recognition and get fixed
I feel like I'm having a deja-vu. I remember having a similar discussion in the past and it turns out it happened exactly one year ago when Flutter 2 was released: https://news.ycombinator.com/context?id=26336657 Every framework has bugs and feature requests that are fighting for resources. And the ones affecting you _always_ seem more important than the ones that don't. That being said, the fact that memory leaks in…
It looks like you answered yourself, this issue does not seem to affect people. Either it is a rare intermittent or only happen in very specific configurations, either there is a leak but it is negligeable, or shortlived. OR maybe this leak cause suboptimal performance but it must not be "feelable" although you did a great find, this issue has been overlooked and its severity should be better investigated. I'd like to remind you that Ionic is not the point, Ionic is simply a packaging of good practices and optimized components (because yes ion-img implement important optimizations over a normal img tag). Some might have leaking issues but the point is that you can trivially use a standard img tag, or a regular react/angular image lazy loading library or even better https://chromestatus.com/feature/5637156160667648 The web BTW will probably be the first ecosystem to provide support for JPEG XL images, which are a significant evolution in performance. Compare the discussed underinvestigated suboptimality with e.g. this 50% CPU increase over a trivial GIF, and mostly ignored/delayed https://github.com/flutter/flutter/issues/88858 or even https://github.com/flutter/flutter/issues/94205
> Every framework has bugs and feature requests that are fighting for resources. relativism has its limits, chromium has thousands more human resources than flutter and react native devs combined
Earlier quoted context omitted.
I came here to say this too. Build your app as a website, then just use a simple browser window of an app that loads your site. Then you only develop in one place, and have nothing to compile or build. Hardly ever have to update your "app" builds even. This won't replace every app of course depending on what you're trying to do and if it requires specific hardware features, but I'd say about 99% of apps don't need to…
This is also how you lose customers.