Android :: Private Fields Naming Guidelines

Here http://source.android.com/submit-patches/code-style-guide#shortmethods it is stated that :

"Field Names
* Non-public, non-static field names start with m.
* Static field names start with s.
* Other fields start with a lower case letter.
* Public static final fields (constants) are ALL_CAPS_WITH_UNDERSCORES.

also states that : "The rules below are not guidelines or recommendations, but strict rules. You may not disregard the rules we list below except as approved on a need-to-use basis." I don't like the "m" convention before private or package fields in a class... I really find this uninspired. I mean, if we try to apply good designs, the low coupling of the classes implies having few public fields. actually, in my programs I usually have no public fields, even when I need some I use getters and seters. so, why should I be forced to have almost all my fields in the program with an "m" in front of them? wouldn't be easier to have the few public fields, if there are any, with some "g" in front or something? or just use setters and geters as beans suggest? this really makes my code harder to read. also, following these guidelines, local temp variables used in the methods have no restriction so they could easily be mistaken for public global fields (also without restriction). this also I find to be wrong, as it is a probable source of mistakes. I understand to have a way of differentiating from fields, but private/protected member fields are the most used in an application, they shouldn't be less "readable". what do you think? should I follow the guidelines?