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.
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. :)
Comments
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.
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. :)