Hacker News new | ask | show | jobs
by davidkuennen 1507 days ago
Having a cross platform app (Flutter) with tens of thousands of users for a few years now I can tell you that not a single person has cared to far.

I get 20-50 mails daily through a very easy to use feedback and support function, but in none of those thousands of mails has anyone ever cared about how transitions are made or that a button doesn't look like a native iOS button.

They care about the value the app provides. About new functions or (in my case) report bad data to fix. That's why they download an app. Not because they want the button to look natural.

That's to say. I frequently get feedback about how they love the UX/UI of my app.

If there isn't a valid reason to create a native app these days I consider it a waste of time.

3 comments

Can second this. Nobody ever said anything about these subtle details and I think there's a very good reason why that is:

Most native apps also have inconsistencies, lags, delays, especially if they connect to some remote web service. Heck, the iOS settings occasionally hang on my phone when I open the iCloud settings or if some Bluetooth device isn't correctly pairing or whatever.

I've seen beautiful native apps that require an internet connection all the time, because they save every little piece of data on a remote server and sometimes, the whole thing is super unresponsive.

For the muggles, this lag is a lot more noticeable than a transition or a button press that is not 100% optimal.

My Ionic app uses PouchDB and CouchDB, is offline-first/local-first and is responsive at all times, because it simply doesn't care if it is online or not. This is what users feel the most and it can feel a lot better than many internet-connected native apps.

You wrote: <<I've seen beautiful native apps that require an internet connection all the time, because they save every little piece of data on a remote server and sometimes, the whole thing is super unresponsive.>>

I have see this multiple times for enterprise software. It works when the data center is on the same continent, e,g., New York to Chicago or London to Frankfurt, or Santiago to Sao Paulo. Now add 20km+ roundtrip on fibre -- Tokyo to London. It is a horrible user experience. I have seen teams trip over that wire (pun intended) more than once in my career!

When one is drowning in a torrent of superfluous UI changes and the UX mediocrity of Windows, Android or Linux, poor software seems inevitable.

Those that do notice, likely assume that the dev can’t do better or doesn’t care.

What would you do if somebody did complain about your UI or UX, rewrite the framework’s UI controls and animations? Switch frameworks? You’d probably thank them for the feedback and say you’ll add it to your task list, where it will linger for weeks or months until it’s closed “won’t fix” because only few people asked about it.

I notice non-native apps. Even if it is very subtle: Apple has some menus around the iCloud settings interface that are actually a webview.

But what am I supposed to do, mail the dev telling them to make a native app instead? If they haven't made one, I understand that they can't afford it.

The iCloud settings are slow, because the backend is slow, not because it is a WebView.
On your phone, open Settings, then tap on your name (apple id), then tap on "payment and shipping", "subscriptions", or "media and purchases" -> "view account". All of those are webviews.
What's your point? You're just repeating what they said. WebViews which reach out to slow backends will render slowly. That's about it.
I didn't say anything about slow, even though they are indeed slow. All the elements (spacing, sizes, etc) are clearly off.
If you're using that as indication for WebViews than you'll be miss-identifying a lot of native apps as well, because that's all set by the developer - both with native apps and with WebViews.