Hey @elmji - would love to have a discussion on this. Let me know what forum would work best - we can definitely thread conversations in here.
So to start, what do you mean by "Android works better than iOS"? In what way? Was it performance related? Or did you mean more about missing features, unfamiliar design patterns, or other issues? Just wanted to make sure I had the right context.
I know I shouldn't speculate without context but that hasn't stopped me before - so some random thoughts on this :-)
Flutter seems to have more traction with Android developers in general.
My feeling is that this is because they have an advantage over iOS developers in terms of familiarity with the standard IDEs used/advocated. By default, codelabs and tutorials focus on using either Android Studio or IntelliJ IDEA (with Flutter plugins) for development -- and that IDE is intrinsically familiar to the Android developer. I have not developed in iOS but I wonder what the development experience is like for them in terms of getting access to useful tools (e.g, Flutter inspector) and support (e.g., code completion) in their default editors.
Flutter's Android widgets are essentially Material Design components.
At IO I was delighted to see that the Material Design team lists Flutter as an equal target (alongside web, iOS and Android) for their design guidance. To me, that signals that the MD & Flutter teams are likely working together to ensure that the Flutter Android widgets are on parity with the native Android widgets for Material Design -- which may result in the design options and process being intuitively more familiar to Android developers and the release cycles being closer together. By contrast, with iOS, I would assume they have to do additional work to release iOS-compliant widgets on parity with Apple's updates.
Not sure if that helps - but would love to get concrete details on what issues you are facing and have a great discussion.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey @elmji - would love to have a discussion on this. Let me know what forum would work best - we can definitely thread conversations in here.
So to start, what do you mean by "Android works better than iOS"? In what way? Was it performance related? Or did you mean more about missing features, unfamiliar design patterns, or other issues? Just wanted to make sure I had the right context.
I know I shouldn't speculate without context but that hasn't stopped me before - so some random thoughts on this :-)
Flutter seems to have more traction with Android developers in general.
My feeling is that this is because they have an advantage over iOS developers in terms of familiarity with the standard IDEs used/advocated. By default, codelabs and tutorials focus on using either Android Studio or IntelliJ IDEA (with Flutter plugins) for development -- and that IDE is intrinsically familiar to the Android developer. I have not developed in iOS but I wonder what the development experience is like for them in terms of getting access to useful tools (e.g, Flutter inspector) and support (e.g., code completion) in their default editors.
Flutter's Android widgets are essentially Material Design components.
At IO I was delighted to see that the Material Design team lists Flutter as an equal target (alongside web, iOS and Android) for their design guidance. To me, that signals that the MD & Flutter teams are likely working together to ensure that the Flutter Android widgets are on parity with the native Android widgets for Material Design -- which may result in the design options and process being intuitively more familiar to Android developers and the release cycles being closer together. By contrast, with iOS, I would assume they have to do additional work to release iOS-compliant widgets on parity with Apple's updates.
Not sure if that helps - but would love to get concrete details on what issues you are facing and have a great discussion.