4 ms·
I have almost no mobile app development experience, so take this with a grain of salt, but it seems to me like the reason you wouldn't have to worry about an An
by m0th87 17y ago
I have almost no mobile app development experience, so take this with a grain of salt, but it seems to me like the reason you wouldn't have to worry about an Android app wrecking havoc on your smartphone is because it runs in a JVM-ish sandbox, whereas iPhone apps have unfettered access with Obj-C. The Android technical environment is self-regulatory, whereas Apple has to bolt-on a bureaucratic process to ensure quality.
- ryanpetrich 17y agoThe iPhone OS also runs a sandbox, but it's much less restrictive than it should be. Often public API's will just use a private API or write to an SQLite database directly; this behind-the-curtain behaviour could be replaced by background daemons wired up to the public API's. Just because an application is native doesn't mean the kernel doesn't protect the OS from rogue processes; desktop/server OS's have been doing this for ages.
- thwarted 17y agoI don't know if that's how I'd describe it but, but one thing Android has is that each app needs to assert the capabilities it needs to run (can make phone calls, can keep the phone from sleeping, can access GPS info, can read anything on the sd card, will store data on the sd card, etc), and will not be able to do things it doesn't assert it needs in the manifest (this was actually a minor problem early on because the string for GPS access was unknown/documented wrong). And at least at install time, users can see these permissions so they can be aware of what they are getting into.