Say I have a measurement field in my app that takes a decimal:
Google's dev guide says that floats are bad, because the embedded hardware does not have floating point number support like desktop CPUs do.
And creating objects should be avoided too, if possible, because it is an expensive operation in an environment with limited resources. Garbage collection of objects used in UI code can lead to 'hiccups' in the user experience too.
So if a float is out, that leaves us with double, right? The best solution appears to be this:
double value = Double.parseDouble(txtInput);
I think parseDouble is better than valueOf, since we probably don't want to be doing any auto-unboxing.
Note: I include these lines in the layout xml to restrict the field to a single-line decimal input:
<EditText .... android:singleLine="true" android:inputType="numberDecimal" ... />
The inputType also sets the soft keyboard (popup keyboard) to the numeric keyboard.