Yes, exactly, it's very open to debate what safety in this case actually means. I think what is meant by safe in this context is that an that is not an in

Yes, exactly, it's very open to debate what safety in this case actually means. I think what is meant by safe in this context is that an that is not an input method cannot pretend to be one. But is that really a concern? If you're putting together a spyware app disguised as a keyboard, why not just include a keyboard and "fool" this protection by actually providing the advertised functionality? I also believe that the Android people in this specific case define "safe" as "safe from crashes" in the way that a 3rd-party external component cannot easily crash the foreground app because of the windowing and thread-based compartmentalization.