On 8/4/2011 8:42 AM, Joe Pluta wrote:
Just to be clear, you can do most of your development in the
emulator.

Only Joe would program a phone in a 5250 emulator. But it would still be some of the slickest code around. <grin/>

Seriously ... this I knew. I have the Android SDK on one of my machines.

It's not blazingly fast, but on a decent workstation it runs just
fine.

That's to be expected.

After that, sending the app to your phone is easiest using Dropbox.

This is good to know.

The only thing is making sure your phone accepts third party apps
(usually just a setting on the phone).

Is this what is called 'side loading'?

I think I heard there was a problem with that on AT&T phones at one time ... but it went away.

For that, just about any phone works. I like my Samsung Fascinate;
it's just the right size for me.

Yeah, that's why I'm shopping around.

I would have gone with the Samsung Nexus yesterday ... but the lack of expandable memory gave me pause.

On the other hand, if you plan on doing crazy stuff (rooting the
phone, installing a new copy of the OS, etc.) then you need to read
the blogs and find out which one seems the easiest to upgrade. I
haven't gone that route yet.

Oddly enough, I tend to stick with the stock OS on my phones ... I jail broke my iPhone's a few times, but always went back to the Apple OS within a few days.

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.