Hacker News new | ask | show | jobs
by Touche 4597 days ago
nit: you want to deliver the best possible ui experience. UX encompasses more than just the ui.
3 comments

Agreed. One of the primary annoyances of HTML5/PhoneGap (as of a year ago or so), was that load times were slow and the UI wasn't as responsive as it should be. It never felt awesome to me.

For me, and maybe it's just me, I can build a much better experience using native code. I also can tweak some very small, but important details that HTML5 doesn't let me tweak.

If someone can create the same experience better, cheaper, and faster using HTML5, more power to them, but I can't, so I go native.

I haven't seen anything in the last year to say that a whole lot has changed. If anything, a lot of major projects have tried HTML5 and have "gone native". I realize there are plenty of projects that might prove the opposite, but when you are just one or two guys cranking out an app on iOS or Android, well you make the best decisions you can and move on.

Exactly, and you don't want to use a document mark-up language patched up with scripts for your UX.
If UX encompasses UI, how is saying that he wants 'the best possible user experience' incorrect? UI performance and bugginess has an effect on user experience.
UX is a superset of UI. That native delivers a superior UI doesn't mean it delivers a superior UX.
I'm just counter nitpicking at this point which isn't much better.

> That native delivers a superior UI doesn't mean it delivers a superior UX.

Sure, it doesn't necessitate a superior UX, but it certainly has an effect on UX. Here 'programminggeek' has tried building apps using native and using web technologies and has found that, for him at least, native provides a better UX. Are you saying thats not possible? That the choice between native and web is absolutely not a UX one but a UI one?

I'm saying that the web has UX benefits as well. The implication of the parent's post was that if you value UX native is the only choice.