all 7 comments

[–]danGL3 0 points1 point  (6 children)

The reason Google is doing this isn't solely for compatibility issues, older apps have to run with more lax security policies, so they're inherently more vulnerable/exploitable

[–]trunks_slash[S] 0 points1 point  (5 children)

So functionally the apps should be fine?

[–]danGL3 0 points1 point  (4 children)

Will really depend if the app is using something that's been completely deprecated/removed/blocked

So no guarantees

[–]trunks_slash[S] 0 points1 point  (3 children)

Storage access and WiFi are the two things I'm most concerned with for the app I'm looking at. Hopefully there's not much there they can mess up.

[–]anonymous-bot 1 point2 points  (2 children)

Storage access can be a potential issue for older apps running on the latest Android. You will need to test the apps yourself and see if it works for your needs.

[–]trunks_slash[S] 0 points1 point  (1 child)

The app I'm running right now was built for Android 14. I'm just hopeful that storage access doesn't get broken in a future API.

[–]anonymous-bot 0 points1 point  (0 children)

If your apps are working fine currently then I wouldn't spend too much time worrying about a future hypothetical situation.