Re:Lessons learned from migrating a native iOS app to Flutter
by akmarinov on Sunday January 09, 2022 @10:44AM
(#29864197)
It does matter, I skip using a lot of airline apps and some bank apps, because of the horrible experience they provide.
It’s easier to do it via their website.
Re:Lessons learned from migrating a native iOS app to Flutter
by kjaftaedi on Sunday January 09, 2022 @10:59AM
(#29864366)
You're equating horrible experience with cross platform architectures, whereas there are any number of reasons apps can be bad.
It is perfectly possible to build a poor app in any language.
Re:Lessons learned from migrating a native iOS app to Flutter
by josefrichter on Sunday January 09, 2022 @11:36AM
(#29864788)
Well that’s the point. While it’s perfectly possible to build a poor app in any language, it’s almost impossible to build excellent app in cross-platform framework. The reason why you recognize them almost immediately is that there are some people obvious annoying details - scroll lag, non-standard UI elements, non-standard navigation patterns, you can just immediately feel something is wrong, even if you are a normie. It can be partially compensated by the app having some other great benefits.
Re:Lessons learned from migrating a native iOS app to Flutter
by fauigerzigerk on Sunday January 09, 2022 @12:05PM
(#29865127)
I disagree about scroll lag. There are plenty of WebView apps (and websites obviously) that have zero scrolling issues.
Non-standard UI elements is something I don't personally care about. Some people do, but I think this is an issue that is often overstated (or perhaps rather overestimated as a factor) by platform enthusiasts.
What does matter a great deal to me though is launch speed and battery usage. Mobile apps are often used for short periods of time. They must launch instantly. And battery is the scarcest resource in mobile computing.
Nobody will voluntarily use an app that is slow to launch and shows up at the top of the battery usage table in spite of only having been in use for a few minutes.
As a developer, these are the issues I would like to learn more about in respect of any new cross-platform technologies.
Re:Lessons learned from migrating a native iOS app to Flutter
by warning26 on Sunday January 09, 2022 @02:21PM
(#29866452)
> While it’s perfectly possible to build a poor app in any language, it’s almost impossible to build excellent app in cross-platform framework.
100% this. Cross platform frameworks will always fall into a weird uncanny valley where there are just things that are subtly off about apps made with them. Most of the user base may not be able to pinpoint exactly what's wrong with such apps, but I believe they still notice on some level.
Re:Lessons learned from migrating a native iOS app to Flutter
by a5aAqU on Sunday January 09, 2022 @03:26PM
(#29867001)
I rarely notice unless the developer hasn't put any effort into the UI. Most people don't care.
Re:Lessons learned from migrating a native iOS app to Flutter
by josefrichter on Sunday January 09, 2022 @04:08PM
(#29867349)
Of course they don't care. But you can feel the experience is not spotless.
Re:Lessons learned from migrating a native iOS app to Flutter
by a5aAqU on Wednesday January 12, 2022 @01:22PM
(#29910810)
I usually don't notice or care, unless they haven't put any effort into it. Now that I'm thinking about it, there are a few that I suspect aren't native, and I don't get bad feelings from the apps unless they are badly programmed and the functionality doesn't work.
Re:Lessons learned from migrating a native iOS app to Flutter
by Apocryphon on Monday January 10, 2022 @03:08PM
(#29881317)
But if they don't care, why does it matter what they feel?
Re:Lessons learned from migrating a native iOS app to Flutter
by josefrichter on Wednesday January 12, 2022 @07:20AM
(#29905354)
What I mean is they don't actively consciously care. They have better things to do. But they're not immune to perception. They do have some impression and experience that they're also likely to be able to express in the form of feelings.
Re:Lessons learned from migrating a native iOS app to Flutter
by skavi on Sunday January 09, 2022 @03:19PM
(#29866941)
Even the best Flutter apps feel awful compared to a decent native iOS app. Which honestly sucks, because I much prefer writing Flutter apps to anything else.
Re:Lessons learned from migrating a native iOS app to Flutter
by Jcampuzano2 on Sunday January 09, 2022 @11:08AM
(#29864459)
Unfortunately the horrible experience is much more normalized with the amount of bloatware and horrible ux software out there to the point that users will use it either way in many cases.
Re:Lessons learned from migrating a native iOS app to Flutter
by poopooracoocoo on Tuesday January 11, 2022 @09:27PM
(#29901532)
And truth is, as long as you have exclusive content on a service, the quality of your app (and thus the satisfaction of your end users) doesn't matter all that much.
Re:Lessons learned from migrating a native iOS app to Flutter
by edf13 on Sunday January 09, 2022 @11:00AM
(#29864378)
This comment applies equally to native as it does cross-platform frameworks
Re:Lessons learned from migrating a native iOS app to Flutter
by eklavya on Sunday January 09, 2022 @11:18AM
(#29864562)
And yet those businesses continue with the app they have. That tells that the vast vast majority of their clients don't care or are happy with them.
Re:Lessons learned from migrating a native iOS app to Flutter
by a5aAqU on Sunday January 09, 2022 @03:31PM
(#29867037)
I'm not sure why you're getting downvoted. I often don't notice, and I've never heard anyone comment about those things. Most end users don't even know what those platforms are. Some apps look different than others just like some websites look different than others.
Re:Lessons learned from migrating a native iOS app to Flutter
by bartvk on Sunday January 09, 2022 @12:35PM
(#29865445)
Or just suffer through.
Re:Lessons learned from migrating a native iOS app to Flutter
by tambourine_man on Sunday January 09, 2022 @11:42AM
(#29864854)
That’s not how cause and effect work.
Re:Lessons learned from migrating a native iOS app to Flutter
by spiderice on Sunday January 09, 2022 @03:26PM
(#29866998)
I hate when people bring up VS Code in defense of electron. It is basically the one application built in electron that isn't obviously significantly worse because of it. And it's because it is backed by a trillion dollar company that can afford to invest the time to fix the electron limitations for their project. No other app built in electron is even remotely close to VS Code, which is still noticeably bad in performance when compared to native editors.
Re:Lessons learned from migrating a native iOS app to Flutter
by surfmike on Sunday January 09, 2022 @03:50PM
(#29867195)
Slack, Spotify, and Obsidian.md are other apps where I couldn’t really care that it’s using electron.
Re:Lessons learned from migrating a native iOS app to Flutter
by josefrichter on Sunday January 09, 2022 @04:07PM
(#29867343)
Slack and Spotify are not great. You can tell they're electron. I don't know Obsidian.
Re:Lessons learned from migrating a native iOS app to Flutter
by pacomerh on Sunday January 09, 2022 @09:53PM
(#29870038)
It's still used by millions, so I would say it's a success
Re:Lessons learned from migrating a native iOS app to Flutter
by pjmlp on Monday January 10, 2022 @02:11AM
(#29871529)
I use Electron based apps, because they are part of the job, refusing them means looking for another job, which in the current world status is kind of not really what I want to do.
The path to sucess is a very tortuous one full of victims.
Re:Lessons learned from migrating a native iOS app to Flutter
by howinteresting on Sunday January 09, 2022 @03:49PM
(#29867189)
1password 8 is also very good, being built in Electron with a Rust backend.
Re:Lessons learned from migrating a native iOS app to Flutter
by mandrizzle on Sunday January 09, 2022 @05:11PM
(#29867841)
Is it better than the native 1password7?
Re:Lessons learned from migrating a native iOS app to Flutter
by howinteresting on Monday January 10, 2022 @12:56AM
(#29871162)
Personally, yes, I think so.
Re:Lessons learned from migrating a native iOS app to Flutter
by pjmlp on Sunday January 09, 2022 @04:41PM
(#29867584)
Additionally they offload tons of stuff to native code out of process.
Re:Lessons learned from migrating a native iOS app to Flutter
by dmitriid on Sunday January 09, 2022 @01:40PM
(#29866073)
> The vast majority of users simply won't notice and not care at all if
Users will of course notice and care. It's just they are not versed in shitty tech to properly articulate what they notice.
So every time a user says "the app is broken/slow/hard to use/loses data/can't update data etc." quite often it's because it's some shitty wrapper on top of a shitty "web app".
Re:Lessons learned from migrating a native iOS app to Flutter
by bobbylarrybobby on Sunday January 09, 2022 @05:01PM
(#29867756)
It’s not that people like to play the game “spot the non-native app” for fun, but rather that the fact that non-native apps are so easy to spot means they have some obvious deficiencies that become apparent within seconds of use. No one ever said “I can tell this app is non-native because it’s too fast and fluid”.
Re:Lessons learned from migrating a native iOS app to Flutter
by robertoandred on Sunday January 09, 2022 @01:02PM
(#29865730)
I care that VS Code is non-native. Don't you dare move an open file around the file system outside of VS Code, less it thinks it's been deleted. And it still doesn't have the standard macOS file operations available in the window titlebar.
The same has been said for Electron on desktop for years, but look at how VS Code is probably the top editor in use on desktop platforms, and even more demanding audience, like developers, don't really care that it's non-native.