tberthel wrote:
> What are poor developers (Registered with the Android Market) supposed
> to do that can't afford to have a 2 year contract for each Android
> phone?
The same thing that Windows Mobile, Symbian, Palm, and other mobile
device developers have had to do since the dawn of the PDA: t
One solution is "Release Early, Release Often"
(http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html)
You can keep a list of devices you've tested against in your app and if
the app is run on one you haven't tested against you can let the user
know it's untested on
> Maybe some third party will offer such a service.
Remote application testing through paid services like those of
deviceanywhere.com ( http://www.deviceanywhere.com ) could be an
option. This also forms the backbone of "Sony Ericsson Developer
World's Virtual Lab" (
https://developer.sonyericsso
deviceanywhere sucked for J2ME. The phones they have require that
apps have certs for the network provider to install since they do not
have developer settings.
Well at least if they provide Android phones that won't be a problem
anymore. So, I look forward to trying this solution again even th
While, I am on the 2-4 week iteration process this does not replace
real device play testing.
On Nov 13, 2:21 am, Al Sutton <[EMAIL PROTECTED]> wrote:
> One solution is "Release Early, Release Often"
> (http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/a...)
>
> You can keep a l
Here it is, at last, although we mostly needed this before the dev
phone 1 became available:
http://www.deviceanywhere.com/index.aspx?sid=6&nid=81
On Nov 13 2008, 11:23 am, blindfold wrote:
> > Maybe some third party will offer such a service.
>
> Remote application testing through paid services
6 matches
Mail list logo
