会是怎样的表现给用户？

  

一个普通用户不会注意到其中的差别。

顺便说一句：

  

    

一个真正的调试版本支持。开发人员不再需要到Android补充：可调试属性标签在清单 - 构建工具会自动添加属性。在Eclipse / ADT，所有增量编译被认为是调试版本，所以工具插入的android：可调试=真。当导出一个签名的发布版本，该工具不添加属性。在蚂蚁，蚂蚁一调试命令自动插入了android：可调试=true属性，而蚂蚁版本不。如果机器人：可调试=true是手动设置，那么蚂蚁释放将实际做调试版本，而不是一个发布版本

  

The golden rule is to set debuggable option to off prior to releasing your Android application to the public.

What would happen if I leave (forget to turn off) this option on? I mean, how would it manifest to a user?

I tested and saw no difference.

how would it manifest to a user?

A normal user won't notice the difference.

By the way:

Support for a true debug build. Developers no longer need to add the android:debuggable attribute to the tag in the manifest — the build tools add the attribute automatically. In Eclipse/ADT, all incremental builds are assumed to be debug builds, so the tools insert android:debuggable="true". When exporting a signed release build, the tools do not add the attribute. In Ant, a ant debug command automatically inserts the android:debuggable="true" attribute, while ant release does not. If android:debuggable="true" is manually set, then ant release will actually do a debug build, rather than a release build.