@digitalstone : The accessibility. Google has threaten all apps which use accessibility in the past. There is nothing to stop them to do it again.
Not everything google has done is good. We have seen how the android keep tightening up everything, removing many useful API, lock down many things in the name of "security". But some of these don't even have a proper guideline. As for accessibility, how does Google determine if an app is used by disabled user or not? There is no clear line drawn there, it is up to their interpretation. They can use this gray guideline to remove any accessibility powered apps.
Sure, locking everything making it more secure for end user. But think of that someone can snatch your phone when you are using it. It is in unlocked state, so basically they have access to everything. They can set the display timeout to never or 10 minutes, and keep the phone stay awake so it doesn't get locked out until they extracted out all of your data. Google notice this flaw and then proceed to
remove the ability to set display timeout more than 10 seconds, so the thief must do everything within the 10 seconds. Can you imagine what will happen next? How many user will cry out because they can't set timeout more than 10 seconds, just because Google want it more secure for everyone.
There must be a balance between security and usability.
Security at the expense of usability comes at the expense of security. Users will end up finding a way to disable the timeout altogether, making the phone totally insecure.
@Martin : It still the same in Chrome 69 (design have been materialized), RR 6.1 Oreo 8.1. But I actually like it this way, swipe down still have the usual card view, while tapping become list. But somehow the undo button also disappear caused by this. However, Chrome 69 in LP 5.1 doesn't have this bug, undo also works properly. So something in Nougat 7.0+ combined with Chrome 68+, combined with Automagic's accessibility, will result in this weird behaviour.
).
