Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To me the worst side-effect of naively chasing "native" is permission prompts.

The web platform wants to have powerful features that are dangerous and/or easy to abuse, but haven't found a good way to allow them safely.

The "solution" we've settled for is to blame the user for clicking "OK" on permission prompts that have unclear consequences to non-technical users.



That's exactly the same as iOS native permissions, isn't it?


Similar, but the key difference is that Apple can kick the worst abusers out of the walled garden.

The Free Web can't do that (and I strongly prefer it to remain Free with low barrier to entry), so it needs a better approach, or needs to give up on having dangerous features available.


The web platform wants to have powerful features that are dangerous and/or easy to abuse, but haven't found a good way to allow them safely.

The same problem exists on native.


Indeed, that's why I think it's a mistake to copy native with problems plaguing it (when we don't know how to add these features without the downsides).

I'd prefer the Web to stay safe and hassle-free, and use native apps—with the risk of letting malware in—only when I really need more powerful features.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: