Taking the final wrapper off of Android 7.0 Nougat
android-developers.blogspot.com
Taking the final wrapper off of Android 7.0 Nougat
1–10 of 250 posts
Re: Taking the final wrapper off of Android 7.0 Nougat
#2Re: Taking the final wrapper off of Android 7.0 Nougat
#3[0] Sure, better performance is always nice, but I don't care for Vulkan, VR Mode, or Multi-Window.
Re: Taking the final wrapper off of Android 7.0 Nougat
#4Personally, I don't care for any [0] of the new features. This is the greatest feature, because it means Android is mature now. [0] Sure, better performance is always nice, but I don't care for Vulkan, VR Mode, or Multi-Window.
Re: Taking the final wrapper off of Android 7.0 Nougat
#5Re: Taking the final wrapper off of Android 7.0 Nougat
#6If you have a Nexus device and don't care much for the Play Store applications (F-Droid is included) give it a go for a true AOSP experience.
The only apps I'm really missing are Tasker and Signal, but I have a second phone for those.
Re: Taking the final wrapper off of Android 7.0 Nougat
#7(click the Multi-Window support link)
> If your app targets API level 23 or lower and the user attempts to use the app in multi-window mode, the system forcibly resizes the app unless the app declares a fixed orientation.
> If your app does not declare a fixed orientation, you should launch your app on a device running Android 7.0 or higher and attempt to put the app in split-screen mode. Verify that the user experience is acceptable when the app is forcibly resized.
Great, more nonsense being shoved down Android developer's throats. They still claim that newer versions and new features are not breaking their API - if this is the case, why would an app on Google Play from a year ago need the developer to "verify that the user experience is acceptable" just because they published a new version with a new feature?
It's been almost nine years since Android released its initial SDK and they're still playing cowboy stuff like this. This feature should be turned on for apps targeting Nougat or later, you shouldn't make every Android developer check every app ever made because three people on the Android developer team made a new feature and can't wait for its use to become more widespread, so they turn it on by default for legacy (pre-Nougat targeted) apps.
Re: Taking the final wrapper off of Android 7.0 Nougat
#8Re: Taking the final wrapper off of Android 7.0 Nougat
#9> Multi-Window support lets users run two apps at the same time (click the Multi-Window support link) > If your app targets API level 23 or lower and the user attempts to use the app in multi-window mode, the system forcibly resizes the app unless the app declares a fixed orientation. > If your app does not declare a fixed orientation, you should launch your app on a device running Android 7.0 or higher and attempt t…
The logic probably went along the lines of: it's better for the user to have this feature that works with X% of what they already have installed than to force them to wait for the developers of each and every app to decide if/when they want to get around to updating.