Live data from Hacker News

We're forking Flutter

flutterfoundation.dev

251–260 of 748 posts

Re: We're forking Flutter

#251
post #233

Earlier quoted context omitted.

> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell You can't be serious. Maybe on Android, but on other platforms—especially iOS—they stick out like a sore thumb. A number of them just look like Material Design Android apps awkwardly transplanted over, but I know that's down to the developer so I won't hold that against Flutter. But scrolling through th…

Sure, but not every cross-platform app developer wants their app to look "native to iOS". Especially if you want your app to look the same on all platforms and/or have some creative design.

I can appreciate that as a developer, but as a user I don’t particularly care that some company wants to ship identical looking apps on every device under the sun.

I would prefer the apps I use to work and behave in a consistent way, using the same platform idioms I am used to. The software available and how it works was a large part of the reason I chose the platform I did.

Of course, I recognise that, a. most people just don’t care about platform idioms, and b. the choice is often a non-native app or no app at all.

Re: We're forking Flutter

#252
post #184

Earlier quoted context omitted.

>Flutter is the best thing that happened to UI development since Qt. Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell I agree with you that Flutter has been a boon for cross platform development, but to say it's impossible to tell you're using a Flutter app is a bit of an exaggeration. I have no problem identifying Flutter apps. Not that I care as they…

Is the complete lack of accessibility still the giveaway? Last I looked Flutter was a complete nonstarter for accessibility.

Can you elaborate? What's missing that makes you feel confident saying "complete lack of" despite well-documented accessibility functionality (including testing for accessibility)? [1]

[1] https://docs.flutter.dev/ui/accessibility-and-internationali...

Re: We're forking Flutter

#253
post #233

Earlier quoted context omitted.

Sure, but not every cross-platform app developer wants their app to look "native to iOS". Especially if you want your app to look the same on all platforms and/or have some creative design.

The trouble with this is most users only use one platform and so don't care. They just see the app as badly implemented as it does not match other apps on the platform.

Why would an app not looking like a native app automatically be seen as badly implemented?

Re: We're forking Flutter

#255
post #171

Earlier quoted context omitted.

No Eric founded Flutter at Google. However, Google had previously acquired another company called Flutter, and they had that domain lying around, and decided to use it. That's what I understood, at least.

Gotcha. To use "Founder" then seems like a weird choice? I guess, I must catch up to the changing meanings of words used in SV.

founder is a word that exists outside the context of SV and has never exclusively been the domain of startups.

Re: We're forking Flutter

#256

If someone could do the same with Xamarin/Maui that would be awesome! It’s going down the same path unfortunately as Flutter did. Microsoft has de-staffed and deprioritized Xamarin/Maui to a point most of the folks are in Aspire-dotnet and related efforts?

It's such a shame mobile development with C# isn't more viable. I want to make some apps, and I hate JavaScript, but from everything I've read Maui just isn't practical.

Re: We're forking Flutter

#257
post #239

Earlier quoted context omitted.

> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell You can't be serious. Maybe on Android, but on other platforms—especially iOS—they stick out like a sore thumb. A number of them just look like Material Design Android apps awkwardly transplanted over, but I know that's down to the developer so I won't hold that against Flutter. But scrolling through th…

Flutter showcase is a disgrace, to be honest. Doesn't represent the actual landscape even remotely.

That is good to hear and hopefully gets fixed. It has been some years now, but I did use flutter for some toy projects and liked using it - I am used to using ReactJS I found there was a lot of transitive knowledge coming from that background.

Ultimately what dissuaded me from pursuing it for any bigger projects is a lack of examples of great looking production apps with complex requirements. When I was looking, I was seeing a lot of CRUD apps - display a form, click an upload button, ect. This was probably 2018/2019 when I was taking a serious look at it.

All of that is to say: Quality app showcases do matter for whether or not devs will trust a solution enough to pull the trigger.

Re: We're forking Flutter

#258
post #233

Earlier quoted context omitted.

Sure, but not every cross-platform app developer wants their app to look "native to iOS". Especially if you want your app to look the same on all platforms and/or have some creative design.

The trouble with this is most users only use one platform and so don't care. They just see the app as badly implemented as it does not match other apps on the platform.

What kind of users/apps are these? I'm genuinely curious about this, actually. I have a couple of apps with 100K+ installs, and I talk to people who are actual users from time to time. I have never ever heard the claim that they don't like UI because it doesn't feel native. Like ever. But I can imagine that in some niches/demographics/app types it might be different. Can you share some evidence or explain how you built the understanding that users dislike non-native UIs?

Re: We're forking Flutter

#259

This is a welcome fork. Still for me, flutter is not web platform friendly by design(e.g. javascript) and that's the reason I stopped using it and switched to react-native + electronjs(react), they seem more reliable and production ready, plus this approach is totally web friendly.

I had the same thought and ended up learning swift and out had been great.

Re: We're forking Flutter

#260

Earlier quoted context omitted.

Google is the „owner“ of flutter, why would they fork their own thing? The post is describing the problem the author has with google.

But they're using the Flutter trademark. It's a fair question. They appear to be using a trademark owned by someone else without permission.

Right, give it a few days and the domain will change.
Post reply on HN