|
|
|
|
|
by dmitriid
1264 days ago
|
|
> Not sure how much of that is necessary. I mean, a button doesn't "look native", so what? It's a button. Is it? Native buttons also come with things like affordances, accessibility, recognizability. "So what" is what lead Google to spend money on user research involving hundreds of people to figure out that text boxes looking like text boxes is good, actually. |
|
And web views come with things like scaling, accessibility, page/document search. The recognizability and discoverability is up to the designer. Between the two, I miss browser features a lot more than native look and feel.
Then let's not forget the privacy nightmare that mobile apps have been.
I can also often fix poorly built web with some css or other hacks that I cannot do on mobile for poorly built apps. I helped a user do just that the other day, if it had been native he would not have been able to work around the design issue.
The native bias here is crazy. Most users just don't care and can't tell if they are on something that's native vs a web view. What they care about is, does this provide me value? That's real UX. Not blowing out development budgets on duplicating the same features on 3 platforms. You can spend that potential budget on refining and improving the features.
Does it matter sometimes? Yes! The are limits to what you can reasonably do in a web view. But most of the time a web view works fine.