Hacker News new | ask | show | jobs
by discreteevent 3178 days ago
Fair points. It's worth stating though that this only matters if you have a requirement to look 100% native. Many apps don't have this requirement whether mobile or desktop and so they may use a web ui. In our case we didn't have the 100% native requirement and used Qt. We still had a really slick user interface, it just wasn't native.

Note that our customers are primarily concerned about the functionality of the app: They are not drive by consumers, they come to the application because of it's functionality. I understand that not everyone has this kind of customer.
1 comments
Illniyar 3178 days ago
It's not just about the look, it's about the feel.

From looking at the "gallery app" on android:

Flutter's input-text has their own custom mark text handler - no double tap, long press opens a custom menu that is missing native options (Such as translate text).

Changing the font size in the OS does nothing in the app.

Clicking on buttons doesn't make a tap sound if the "sound on tap" option is set.

I'm guessing no accessibility support - or very poor one.

There's probably many more tiny issues that customer's will complain about when you a product is shipped to production that will make it clear that this isn't a native app.

link
Hixie 3177 days ago
A lot of those are things we've fixed since we published that app. We're just not very good about publishing updates to the play store. I'll see if we can get an update out soon.
link
sethladd 3178 days ago
(disclaimer: I work on Flutter)

Thanks for your feedback! I opened https://github.com/flutter/flutter/issues/12438 to track the "not playing a sound when tapped". We're currently working on improving our accessibility support.

link