Yes, you can use reflection to "check for" and "access" newer apis.
I use it to ship one app that "upgrades" functionality based on the phone (if you start with a new app now, then it would downgrade). If you want, you can even access different "non-api" service methods differently based on the phone (background playback being one whose built-in service is not normally accessible and is different between htc and google devices). rob On Jan 18, 8:14 am, Phil <[email protected]> wrote: > Given the fragmented situation with Android - at least three different > versions in circulation right now - I wonder if somebody can answer a > question for me. Simply put, is the Java compiled down for the Dalvik > VM late binding in the way Java is? It strikes me that if it were, > developers could write applications that adapted themselves to the > Android version and hardware platform they were being run on - having > a 'lowest common denominator' core program that would be more > functional on some hardware, or under later OS versions. > > My suspicion is that it is not - otherwise there would be fewer > complaints about fragmentation. Comments from somebody more in the > know that I am? > > I feel Google has missed a trick here - I can understand the reasons > for not just using/licencing Java (cost and control) but Android won't > be able to deliver maximum benefit for Google or Joe Public as long as > there are multiple (apparently incompatible) versions in production > and network operators/hardware manufacturers aren't able to keep > reasonably up-to-date.
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
