best phone for developing?

-

 

     So you are an Android developer now? great. you’ll probably start to develop using eclipse and some emulators (probably min 2.2). most of the developers I know are a bit fed up by the fact that the emulator suffers from a “few” cons. like what?

  1. You can’t really use an emulator with a mouse and get a real feel the same way you’ll do using your fingers and the various gestures you’ll use on an actual phone – get a real phone
  2. if you’re developing an app which includes picture taking/video recording or sound even, then you’ll find yourself guessing – get a real phone
  3. Locations – yes, if you’re developing an application which includes locations and maps, you’ll probably want to test it out. yes, the DDMS offers such emulation of Geolocations but it’s not so fun to use – get a real phone
  4. pretty much any sensor that you can’t think about needs a real phone in order to develop it the proper way – get a real phone

 

ok, we got it, you need to get a phone.

which phone? so many resolutions and API versions? should I get 3-5 different devices?

probably no, if you’re just starting to learn how to develop android apps, you’ll probably be using a basic device which doesn’t have to include massive processing power.

My recommendation is to get a Samsung galaxy S, as much as I am a HTC guy to the bone, the Galaxy S has shown great performance over the years and has been my favorite device to debug on, as someone I know used to say – “if it works on Galaxy S – it will work everywhere”

Comments

Post a Comment

Popular posts from this blog

Spinner VS AutoCompleteTextView

-
Image
       We’ve all been in a situation where we needed to show a list of some sort, a list which should be triggered by a user interaction (click, tap, etc..) A list is simple enough, probably even a spinner if we don’t want to spend that much screen real-estate on showing a list which the user clicks once and probably doesn’t need to see it after that. A spinner can be a real bug once there are too much entries for the user to choose from, how much is too much? that’s a good question – probably it differs from user to user, and probably this will have some performance issues with areal large number of entries, you cannot scroll forever to find what you’re looking for. A simple solutions for the problems mentioned above is an AutoCompleteTextView. it’s a control which is basically a combination of a TextView, EditText, and a Spinner all wrapped up in a single easy to use and configurable control. let’s see how it’s done:   first, in the layout file, create an AutoCompleteTextView
Read more

How to update UI from a different thread

-
     Google has set it’s tone on some tough guidelines for developing android apps, basically there aren’t any strict rules but one very easy to misunderstand. there is a single Thread which is called the “main” thread, or “UI thread” on some places. this is the thread which is in charge on the views and interaction with the users gestures. based on the guidelines of any mobile platform at the moment, all the work that shouldn’t be done on the main thread should be done on background thread. this can be achieved in many ways, you can use AsyncTask, Or A Handler, Or a simple thread with an implementation of the   run() method within the declaration of the runnable. ok, so if I’m pulling some server data, or performing long calculations, pulling stuff from or to the Sqlite database I’ll probably use an AsyncTask. but let’s say for instance that I want to simply update the UI once every couple of seconds (update a TextView or an ImageView’s content etc..), here’s a simple example of i
Read more

Utilizing Http response cache

-
     A typical mobile application will probably consume some resources from a web server using http requests. This repeated task has some drawbacks: Bandwidth has a cost, polling the same data over and over again results in a waste of user’s quota. the responsiveness and user experience is compromised once the user keeps waiting for data. If the requested data hasn’t changed on the server, then there’s no reason for us to fetch it. Of course, local caching of data is a must, but we also need to be able to refresh the data if it has changed on the server. A simple solution which comes out of the box for API 4+ is http response caching. Http response caching is a mechanism which enables us as developers to save a footprint of the response utilizing the abilities of the Http protocol. Basically, is holds a simple cache of the response which can be defined and enabled in code, and it prevents from fetching unchanged data from the server which was already fetched and processed into t
Read more