A salient quote: "Fragmentation is not really an issue, despite what
you might hear. The underlying Android layout system scales your app
almost perfectly for the different screens. Some tweaking is
inevitably required, but web-development is certainly more difficult.
Writing code that works on 1.6 but takes advantage of 2.2 is really
easy, and the sort of thing you have to do on iPhone too. Nobody has
to compromise. The fact that multiple vendors have customized their
Android distribution is barely a problem."
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.
(*) It really depends. In the past months, there has been a
consolidation on Android 2.1/2.2 and 1.5 devices have been greatly
reduced in percentage. If you're interested in percentages, you could
just ignore them, especially if you start developing now. Unfortunately
I can't, since I've some 1.5 users and I promised not to abandon them
too early. It has to be seen what will happen with 2.3 and 3.0, of course.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
[email protected]
--
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.
