Is it worth purchasing Google Android Dev phone? [closed]

I've been intrigued by all the android world since I first learned about it and would like to get my hands dirty developing for it. The question that comes to mind is if it's worth buying the unlocked phones that Android sells directly or not.

Those phones (link) quoting the Android page:

Run and debug your Androidâ„¢ applications directly on a device. Modify and rebuild the Android operating system, and flash it onto a phone. The Android Dev Phone 1 is carrier independent, and available for purchase by any developer registered with Android Marketâ„¢.

Please note that this device is intended for development purposes, and may not include certain features found on consumer Android devices.

So will it be worth it to purchase one of those as a tool for app testing as opposed to developing and testing just on Eclipse or one of the other IDEs and emulators.

-Have you tried it, do you own one? I'm assuming they have the same specs as the HTC Dream and the HTC Magic, since they look exactly the same although they have a 'developers edition' custom black design not that I really care about the design for this particular item.

All comments are welcomed, Thanks in advance.

Update:

I'll leave it open until tomorrow to see if there are any more answers, then I'll just pick the most voted since it's really a subjective question with no good or bad answer.


Asked by: Marcus282 | Posted: 20-01-2022






Answer 1

It depends what sort of applications you wish to develop. I find that the emulators very accurately reflect how things work on genuine devices; you can seamlessly connect to either an emulator or a dev phone using the command line tools, the Eclipse tools, the debugger etc. Also, while you can flash your dev phone to a new OS version, HTC often lag behind (e.g. there's still no 2.0 image available) and it's much easier and faster to just use the emulators. The emulators also allow you to create and test with different screen resolutions, whereas the two dev phones available are only "standard" resolution.

I find it's quite rare that I need to use my ADP1 dev phone for development -- my rooted consumer HTC Hero works fine for most of the development I do.. allowing me to pull files from the device etc. Though the only reason I use my Hero rather than an emulator is because I've been working on an app that uses audio recording functionality.

However, where having a physical device would help is where you need to do specific stuff regarding the camera, audio hardware, orientation and compass sensors, GPS, wireless network access and so on. Should you need to connect a debugger to work on hardware-related issues like the above, then you would definitely need a dev phone.

Overall, it's definitely worth buying an Android phone for testing and demonstration purposes, but whether it's a development phone is up to your requirements.

Answered by: Kellan459 | Posted: 21-02-2022



Answer 2

If you plan on developing apps that you intend to put on the Android marketplace, it's absolutely critical to test on real hardware. You can get away with developing on the emulator for quite a while, but at some point, you'll want to use a real device.

That being said, you can use any android phone for development. There are some restrictions on locked devices, but if you're simply developing against the SDK, any phone will work. With android, you can install an apk directly on the phone without special permissions, so the only real advantage to a dev phone is that you can install new roms without having to root the phone.

Personally, I'd hold off on purchasing one of the older dev phones. From what I understand, they only support up to SDK 1.6, whereas the Droid and some of the other new phones are supporting SDK 2.0 ++.

Answered by: Ada440 | Posted: 21-02-2022



Answer 3

Wait for the release of the Nexus One from G. The latest rumors are that it'll be released on Jan 5th. So it's just a week or so.

Answered by: Ryan383 | Posted: 21-02-2022



Answer 4

I think that you need a real android device whether it's the dev phone or another handset but a real phone is primordial. The emulator is great but you can't get an idea about the execution speed of your app until you use it on a real phone.

As said before there are a lot of rumors about the nexus one so wait and see!

Answered by: Fenton376 | Posted: 21-02-2022



Answer 5

As for which phone to buy (assuming you're going to get one) I think ablerman is right. I'd wait until January to see if there is going to be some new hardware available.

With regards to the more general question of should you buy one, I think it depends on what you're doing. For the most part, the emulators are fine. They can emulate GPS (you can even load KML to simulate a path), SMS, phone calls, etc. They cannot however emulate acclerometer/compass/orientation sensor data and actually will crash (actually I believe it hangs...) if you try to run code that relies on it. Also, it's difficult to actually debug phone-call related functionality without the dev phone.

They're good phones, I've used the Dev phone 1 (the G1/Dream) and it's nice. It also is a bit faster than the emulators and if you're writing something like a game, it would be really good to test it on the actual hardware.

All in all, it just depends on what you're writing. They're definitely fun to play with regardless as you can do pretty much ANYTHING you want on them.

Good luck with the decision!

Answered by: Rebecca803 | Posted: 21-02-2022



Answer 6

I've been developing with the emulator since June. I've found it to be a very near substitute for the real deal, and it's easier to switch between handset configurations/versions. However, not knowing how quickly my apps will run is a concern for me.

The reason I've personally held off buying a handset is that 2009 was the wrong year to buy one. I have a feeling 2010 will very much be the long-awaited "Year of the Android".

Answered by: Hailey293 | Posted: 21-02-2022



Answer 7

+1 to Christopher and I will add - the emulators are great but having a physical phone will give you instant access to the Android Market to verify publishing, statistics and user comments. I also believe using your own app on a physical phone will help you to develop a better app. You do not need a development phone - but at least one physical phone - absolutly.

Answered by: Chelsea503 | Posted: 21-02-2022



Answer 8

FYI. Belgium is one of the few countries where it is possible to buy any mobile unlocked. Indeed, the Belgian regulators forbid the forced bundling.

Answered by: Miranda289 | Posted: 21-02-2022



Answer 9

One more Pros for buying a real developer phone :

HierarchyViewer does not work on user builds (i.e. with devices available in stores.) This is for security reasons.

See the original thread

Hierarchy viewer can be very useful if you have problems with layout being slow, although I don't think it would worth buying a real Developer phone only for this.

As some people made workaround for that problem : https://stackoverflow.com/a/7801475/62921.

Answered by: Melissa829 | Posted: 21-02-2022



Similar questions

Do in-app purchasing providers like Zong, Paypal, and Boku violate iPhone and Android terms and conditions?

I know there are questions posted elsewhere about how to implement in-app purchases on iPhone and Android, but none answer the legality of the solutions today. At the time of release, there was some dispute over whether some of these solutions violate terms of service, but it's now several months later. There are also now several exceptions like Amazon, which seem to circumvent iTunes for purchases. Anyone have a...


Android In App Billing - how to change a boolean value upon purchasing in app product

I want to implement In app billing to enable a particular feature with my app. I've modified the Android sample code and it is working fine. However, now I need to implement the change to my app once the user buys the in app product. My plan is to have a boolean value set to false and once the users buys the in app product, the boolean value will be set to true and then a previously hidden button will be revealed. My q...


billing - Android - In-app purchasing issue

I'm implementing in-app purchasing in my application. When i test that im keep getting "Purchase canceled Your payment could not be processed" issue all the times. Im using test account for testing purpose and dummy credit card number for purchasing the in-app billing. I added my test account in my market profile. How to test in-app with sandbox number. please help me. NOTE: Would like to implement Auto Renewal f...


android - Unable to request item data for Amazon in-app purchasing

I'm trying to set up in-app purchasing for the Amazon App Store, but am running into a problem when trying to request item data. I'm debugging on a Kindle Fire. Here's my code and what I see in LogCat: @Override public void onStart() { super.onStart(); PurchasingManager.registerObserver( new AmazonPurchasingObserver( getActivity() ) ); PurchasingManager.initiateItemDataRequest( SKU_SET ); }


android - Ensure item is purchased before allowing to download from my server when download is invoked later after purchasing

I have the following scenario: I have some items that I want to sell User buys the item and it is marked is "Purchased". Now user can download the file. User presses "Download" button and downloads the file (it must be some unique link) I read all inapp billing docs and steps 1 and 2 work fine for me. How can I implement step 3 on the android side? I imagine this somet...


android - Purchasing my items as a test with in app billing? (error: RPC:AEC:0)

When I purchase Googles designated 'products' in my android app it runs successfully when I try to purchase my own it asks I enter payment information then upon entering the fake credit card details google provides gives me the error: "ERROR Update could not be downloaded due to an error (error while retrieving information from server RPC:AEC:0" and sometimes:


android - Google in app purchasing get products list

I found the following code from here to get products list from google play store ArrayList skuList = new ArrayList(); skuList.add("premiumUpgrade"); skuList.add("gas"); Bundle querySkus = new Bundle(); querySkus.putStringArrayList(“ITEM_ID_LIST”, skuList); is there a way to get dynamic products list? ...


android - Google Inapp purchasing and trial period

I am building an application which I wish to upload to the app store as a paid app. But i would like to post it as a trial app for a set amount of time. I looked at all the options in the app billing version 3. I have found a few problems. If I create my app with a non-consumable inapp item then i will not be able to keep it for a set duration as a trial app(Please let me know if my assumption is correct)....


android - IAB v3 buy intent is purchasing the item and not consuming it?

im launching a purchase flow with 'android.test.purchased' and that works as expected, however when select 'buy' and completing the purchase it now 'owns' the item and wont let me purchase again, even though i've quite clearly got mHelper.consumeAsync(purchase, mConsumeFinishedListener); NOTE: I'm not getting ANY log feedback until after the purchase and it's telling me the items already owned....


testing - how to test licensed android app(.apk) from android market without purchasing?

I want to test my paid licensed app without purchasing from android market because i want to check it once that the app can download by user or not.And to find any issues with the built(i integrate LVL to my app so i want to test it).






Still can't find your answer? Check out these communities...



Android Google Support | Android Community | Android Community (Facebook) | Dev.io Android



top