Re:Going native
by kangoo1707 on Thursday March 23, 2017 @07:48PM
(#13945403)
If an app can be installed the same way a "native" app does, it is a native app. Users do not care about the technology behind the scene and what they are called.
[ Parent
| on HN ]
Re:Going native
by fnordsensei on Thursday March 23, 2017 @08:18PM
(#13945554)
Aren't we conflating "desktop app" with "native app" in that case? Why do users have to be exposed to the word "native" at all? Just say "desktop app".
Re:Going native
by throwaway2048 on Thursday March 23, 2017 @08:12PM
(#13945518)
They care when an app is a laggy mess that eats battery, cpu and memory like crazy
Java apps could be installed and never used to be considered native. Native means "uses the OS UI components".
So in your opinion, are Cordova apps also native apps?
Re:Going native
by wishinghand on Thursday March 23, 2017 @09:51PM
(#13945930)
All native apps are desktop apps, but not all desktop apps are native apps.
So native would not cover mobile apps?
It depends on the host platform.
On desktop, all native apps are desktop apps but not all desktop apps are native.
On mobile, all native apps are mobile apps but not all mobile apps are native.
This is where I believe we'd differ. Postman already had a "desktop" app in the sense that Chrome apps also existed as desktop apps and when we ask users to switch, they wouldn't.
For most users, desktop apps = things that run on the desktop.
Re:Going native
by wishinghand on Monday March 27, 2017 @11:24AM
(#13968466)
What you say you differ on doesn't seem to be incompatible with my assertion.