Good question. Some thoughts from having done both:
Native apps target a specific platform, and can be optimised for the specific nuances and conventions of that platform. You'll get APIs that are more closely aligned with the particular hardware you're accessing. Done well, a native app can "feel" much more like part of the device. But, you're limited to publishing through the official app stores, and you need to build/tweak the application for each platform you target.
The web, on the other hand, is universally accessible. Put something online at a URL and it can immediately be used by anyone in the world with internet access. The flip side of that freedom is that you can't predict or control how or what device someone will use your application. A good web experience will, by definition, vary from one user to the next.
Users are primarily concerned with doing some task in the most convenient way possible. There's a lot more overhead in downloading a native app from a store than there is from following a link. Sometimes that's worth it in the long run. To pick an approach I'd have to consider the task and decide whether native capabilities are necessary or beneficial to warrant that extra step for the user. If not, I'd go with a well designed website with a PWA to enhance it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good question. Some thoughts from having done both:
Native apps target a specific platform, and can be optimised for the specific nuances and conventions of that platform. You'll get APIs that are more closely aligned with the particular hardware you're accessing. Done well, a native app can "feel" much more like part of the device. But, you're limited to publishing through the official app stores, and you need to build/tweak the application for each platform you target.
The web, on the other hand, is universally accessible. Put something online at a URL and it can immediately be used by anyone in the world with internet access. The flip side of that freedom is that you can't predict or control how or what device someone will use your application. A good web experience will, by definition, vary from one user to the next.
Users are primarily concerned with doing some task in the most convenient way possible. There's a lot more overhead in downloading a native app from a store than there is from following a link. Sometimes that's worth it in the long run. To pick an approach I'd have to consider the task and decide whether native capabilities are necessary or beneficial to warrant that extra step for the user. If not, I'd go with a well designed website with a PWA to enhance it.