> 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.sonyericsson.com/site/global/newsandevents/latestnews/newsoct07/p_p1_added_virtuallab.jsp
). Costs may or may not be prohibitive depending on your budget.

Regards


On Nov 13, 3:11 am, Mark Murphy <[EMAIL PROTECTED]> wrote:
> 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: test on a
> couple, stay within the bounds of device compatibility rules, and rely
> on user feedback for the balance.
>
> Or, only make your application available for sale for devices you have
> tested. I suspect there will be enough information floating around for
> you to have a decent idea what the popular devices are. Just stick to
> the handful of popular ones. Hopefully, the various markets will adopt
> voeveo.com's satisfaction system to help ensure people only buy stuff
> that's supposed to work on their device.
>
> > Which could end up being 100+ phones over the next five years.  Can
> > you really expect developers to have 100k over the next five years
> > just for phone testing.
>
> Forget the money -- you probably don't have the time.
>
> > I would like some kind of deal to get a developer phone for game play
> > testing loaner or permanent.  I wouldn't mind paying with future sells
> > or something.
>
> Maybe some third party will offer such a service.
>
> For simpler apps, an alternative might be what amounts to a
> Browsercam-style VNC setup, where you can test your app on a device over
> the Internet. This won't work for testing out true "feel" (vibration,
> how the trackball works, etc.) and will suck for games with any sort of
> high fps rates. But, again, for simpler apps, it's not out of the
> question someday.
>
> --
> Mark Murphy (a Commons Guy)http://commonsware.com
> _The Busy Coder's Guide to Android Development_ Version 1.4 Published!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" 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/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to