As a mobile developer, I got an email from google saying they’re going to be adding new memory restrictions in apps and it’ll crash if you exceed them.
Thanks google, for buying all the ram, and then punishing us for it.
i can see how this might evolve… someone, the app developer or the user, will end up having to pay google to let an app use more ram than google allows it to for ‘free’.
So, the restrictions are set by the devices OEM and can be based around how much ram the device has, so I think the microtransaction would be with them, not google.
They need this to compete with Apple, apple runs on a lot less Ram because it imposes such limits already, simply by not having as much RAM to begin with
As a mobile developer, I got an email from google saying they’re going to be adding new memory restrictions in apps and it’ll crash if you exceed them.
Thanks google, for buying all the ram, and then punishing us for it.
i can see how this might evolve… someone, the app developer or the user, will end up having to pay google to let an app use more ram than google allows it to for ‘free’.
So, the restrictions are set by the devices OEM and can be based around how much ram the device has, so I think the microtransaction would be with them, not google.
They need this to compete with Apple, apple runs on a lot less Ram because it imposes such limits already, simply by not having as much RAM to begin with
What are the limits? There’s no way this could be done correctly without applying different limits to games vs some compass app or whatever.
Its not explicitly mentioned. Just that itll be variable by the device and how much ram it has and be controlled by the device OEM.
It did talk about how you might get throttled before it crashes as well.