Hacker News Reader

Comment by Sanddancer | Hacker News Reader

To be honest, I don't want a webapp. Webapps may have a good thirty second use case, but adter that, i want something thatnis with all my other programs that I can pin to a menu/quick launch bar, that runs in a different process space so that a bug in a different program doesn't take down your program, etc. I want the same UI/UX as a native app, and that's something tat webapps still fail terribly at.

View on HN

Those sound like an odd bunch of criteria. I'd go for a list more like:

1. Performance (either speed of opening if it's the kind of app you open and close a lot) or just responsiveness in use 2. Quality of user experience 3. Stability 4. Cost. 5. Features 6. Interoperability

At the moment across a range of app types it's roughly 50/50 between web apps and native apps and I occasionally switch alleigence.

Oh silly me for forgetting the markup rules once again. What were those arguments against WYSIWYG again?

I definitely agree (and prefer writing/using native apps), but i would say that uwp apps get all of the UX benefits of a native app (the js apps for UWP get access to all the same libraries as the .net/native apps; I don't know about default styling but I'm sure someone has a template).

Also, UWP apps are full apps like any other windows app.

Totally. I'm writing an app myself using UWP, albeit in C#. I was addressing the wanting it to be a webapp part, not the UWP or written in javascript parts, which is a totally different issue.

Reply on news.ycombinator.com