Hi, Regarding signing the app, I see a third alternative: You can create a distinct key pair to sign their (and only their) app. This way, you can keep the keys, sign and deploy all by yourself for now. If the customer decides to maintain the app without you in the future, you can hand out the keys. If you'd sign with "your" private key, you can not give him the keys and the customer is bound to your key pair for the lifetime of the app. I anticipate he will not like this idea. I would only use a "same key" policy if there is a special reason for this, e.g. you want to share data between the apps.
The decision on which market account to deploy the app is not that important since you can change this later without losing your statistics or download numbers (Notice that the package name of the app cannot change). The Google Market team is very responsive to requests for transferring your app to a different account. Hope this helps, Michael mictale.com/ms -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en

