The developers of standards should think carefully about adding more API functionality, without addressing the issue of implementation standards.
Developers aiming to release products on a wide range of devices (notable game development houses) face a huge and ever-growing cost of supporting multiple devices. This expense will soon become prohibitive for all but the largest companies.
Testing standards for Java applications (Java Verified), driven by device manufacturers, force developers to cope with the failings of the devices they must support. Yet device manufacturers are able to use the Java name, in some cases with a disasterously poor runtime implementation.
In the world of mobile, Java falls short of it's "write once, run everywhere" philosophy.