Androide Oxidado

20.12.2007 @ 14:59 \02\Thu, 20 Dec 2007 14:59:23 +0000\23 +0000 UTC

Android es el SDK de Google para desarrollar aplicaciones en el sistema operativo basado en Linux para mobile devices desarrollado también por Google.

Según algunos reportes, Android está más defectuoso que un auto chino (como los que quieren vender en México) y lo pior es que ni siquiera hay un Bug Tracking System! Esto es algo bastante sorprendente para una empresa como Google.

Según el artículo de Ars Technica:

I put Android to the test myself in an attempt to see how bad the situation really is. What I discovered is a highly promising foundation that is plagued by transitional challenges and a development process that needs more work. Android has many bugs, some of which are impeding development. Unfortunately, Google’s QA infrastructure for the platform is completely inadequate for a project of Android’s scope and magnitude.

There is no public issue-tracking system for Android. Instead, users post information about the bugs they encounter in the Android Developer Google group and hope that one of Google’s programmers sees it so that it can be added to Google’s private, internal issue-tracking system. Users have no way to track the status of bugs that they have reported, and they never know whether the issue is being addressed at all until after it is resolved, at which point it is mentioned in the release notes for a new SDK release.

Esto ha ocasionado que los developers crearan una wiki para darse soporte entre ellos mismos:

This is a pretty clear symptom of a dysfunctional development process. In an effort to minimize the frustration of not having centralized issue tracking, users have started to independently catalog known bugs at an unofficial Android wiki.

La documentación de la API también deja mucho que desear:

Another major problem with Android is lack of documentation. The API reference material doesn’t provide enough information and one sometimes has to experiment (that is, guess) to figure out what the parameters for various methods actually do. In many cases, I found the developer discussion group to be far more informative than the API documentation.

Como pueden ver Android todavía está en paniales. No era de esperarse que Android funcionara a la perfección a la primera, pero creo que la falta de un Bug Tracking System es algo imprecindible para este tipo de aplicaciones.

En el artículo hacen referencia al iPhone y mencionan cómo es que la API del iPhone está específicamente diseniada para su Hardware, mientras que Android está diseniado, o al menos eso pretenden, para una amplia variedad de Hardware:

The inevitable comparisons between Android and the iPhone platform seem a bit misguided now that I’ve really worked with Android. The iPhone platform seems to be tailored to a very specific kind of user experience that is particular to the hardware. Apple has always been good at leveraging the tight coupling between its hardware and software, and the iPhone is no exception. With the iPhone, Apple has sacrificed the potential for hardware diversity but gained in the process the ability to make innovative technologies like multitouch a ubiquitous part of the user experience. Android, on the other hand, has to be designed from the ground up to support an extremely diverse range of hardware devices with vastly different capabilities.

Responder

Introduce tus datos o haz clic en un icono para iniciar sesión:

Logo de WordPress.com

Estás comentando usando tu cuenta de WordPress.com. Cerrar sesión / Cambiar )

Imagen de Twitter

Estás comentando usando tu cuenta de Twitter. Cerrar sesión / Cambiar )

Foto de Facebook

Estás comentando usando tu cuenta de Facebook. Cerrar sesión / Cambiar )

Google+ photo

Estás comentando usando tu cuenta de Google+. Cerrar sesión / Cambiar )

Conectando a %s

A %d blogueros les gusta esto: