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

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

ORM for android

-
     ORM – Object relational mapping has been around for quite some time now. Basically it’s a piece of software (regardless of targeted platform), which simplifies the connection between objects (as in OOP) and data in database (mostly used is tables based relational database), and it exists in order to help simplify bridging the gap between the two in our development process.     Microsoft's Entity framework is a great example for a robust easy to use framework which allows creating and querying the database from an object’s point of view with classic object oriented programming paradigms while maintaining all DB construction’s needs such as relationships between objects (tables) such as one to many or many to many including all the indexing, optimization etc..      In android, we have SQLite as a database platform, from simple to advanced application, it’s likely to assume that we’ll need some relational database to store and retrieve local data from the database using the bas
Read more