|
|
|
|
|
by h2odragon
873 days ago
|
|
"This idea would be too hard / expensive to do ... and someone else already did it" Perhaps the problem lies not in the Internet, but the imagination? Imagine an idea could be implemented without "native apps for both iOS and Android." That said implementation wouldn't need "pay more to get the app noticed through app store paid search." |
|
Having a native app means it is there—you can share things from other applications, and it is easy to see it as a distinct entity that can be opened by clicking on the icon in the app drawer (you can do this with web apps; it's just that now there are load times, you may need to re-login, etc.). Apps allow offline functionality, access to device sensors and features, etc in a more seamless way. I hope the progressive web apps are able to do these things in the future.
In addition to all this, if you are a sophisticated user with an eye for detail, even for native applications, you want the right kind of native app that uses the OS's own widgets, icons, and UI patterns. It is a tough place for new services to gain acceptance.