On Dec 9, 5:22 pm, Fabrizio Giudici <[email protected]> wrote: > While as time goes on I reckon that the fragmentation issue is less and > less a problem (*), the above statement is completely misleading. The > problem with fragmentation, real or apparent, doesn't impact a lot the > *development* (which is addressed by that "writing code that..."), but > the *testing* - both for time, infrastructure and access to physical > devices. Frankly, I'm starting to find that whole interview pretty > pointless.
If you're app just has a GUI that talks to some web page / service (like a twitter app), fragmentation may not be a big issue. I assume that Android fragmentation is more of an issue if you interact with the hardware, such as GPS, camera, Bluetooth and such, because the drivers for these devices may not come from Google, may or may not work properly and may or may not be updated to support the latest SDK properly. Same goes for game (audio and graphics hardware). -- 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.
