> do they believe the required knowledge to write a native app is too obscure at this point to be considered harmful? No, but user expectations about safety be

> do they believe the required knowledge to write a native app is too obscure at this point to be considered harmful? No, but user expectations about safety between native apps and web apps are different. I will say that, personally, I think that native apps place far too little emphasis on security/fingerprinting, and I think that we're kind of ignoring a serious problem with the lack of default sandboxing for native apps. I don't know that it makes sense for every native app on my computer to have this kind of capability. I think most of the native apps on my computer shouldn't be able to access the Internet at all if I'm being honest. But that's just my personal opinion, other people have different approaches/philosophies about software -- and disregarding my own preferences, I think it makes a lot of sense to worry more about fingerprinting in an environment like the web where people are running a lot more untrusted code than they normally would. The web has kind of been a boon for native security, it's really good that users have a quick way to run code that doesn't involve download software and giving it access to their filesystem. It significantly lowers the number of opportunities for attacks. But that only works if the alternative to native apps is both: A) useful enough that users can commonly use it as an alternative to downloading software and running it on their filesystem B) sandboxed enough that it's not just equivalent security-wise to downloading software and running it on a native filesystem. Figuring out how to strike a balance between those two concerns is why thinking about security/fingerprinting on the web is hard.