Some thoughts on finding mobile developers or finding work as a mobile developer

Here is the deal. You want a good mobile app developer, find a good coder, and train him/help him learn.<p>As dinedal noted, it is slow going, as it is outside his day job.<p>There used to be a time where employers would recognize an employee's abilities, and provide for his learning of new subject matter.<p>Sadly, today, you either have to be able to demonstrate the knowledge out of the gate, or be damned.<p>There are plenty of good developers who could easily immerse themselves in mobile app development for two weeks, and become pretty skilled mobile devs in little time.<p>Nobody wants to pay for that, though.

As a developer aspiring to be a mobile developer, I have published one Android app, working on a second, but this is slow going as it is outside of my day job.<p>A question I don't have the answer to is, how do I know when enough is enough to start calling myself experienced? I can launch intents, activities, use SQLite, get to the GPS, Accelerometers, and more, but I have a hard time getting apps to market that prove all of this, since an app is more then just a technical checklist of features.<p>How can I effectively demonstrate to a potential employer I have the technical chops?<p>PS. I can relocate if you were wondering =)

Just by having a reasonably successful non-game iPad app in the App Store, I've begun to receive a number of requests for custom-tailored enterprise versions of the app. I've solved the arguably "hard" problem of larger image viewing within the RAM constraints of the device and have a working, modular set of views that are easily adapted to almost any purpose.

It is a good article, but I think they might overestimate the necessity to have several successful mobile projects under your belt. See <a href="http://techcrunch.com/2010/12/11/the-5-myths-of-building-a-great-mobile-team/" rel="nofollow">http://techcrunch.com/2010/12/11/the-5-myths-of-building-a-g...</a>

Perhaps you can mitigate the "mobile" aspect somewhat. The model and the controller can be written by any competent developer without requiring the mobile skills. Then you can have a mobile specialist developer concentrate solely on the views.<p>At least that's how I am addressing this problem in my application. My mobile interface is just another view that talks to my API. Anyone can write it without having to understand what my application does. I am finding myself writing views for all kinds of environments and it's certainly much easier not to have to change my other code at all. :)