On Apr 25, 2012, at 9:33 AM, Mark Townsend wrote:
> As for Developer Account, it depends on how much control you or the client wants to have over the release process. Doesn't really matter to Apple who's account it's under.
I would strongly suggest that the business have their own developer account, and release the app.
Think about how this pans out in the future -- you decide to do something else, let's say, and on longer do iOS apps. Are you going to keep paying $99/year to keep this business's app in the store?
Or let's say someone else has you do a similar app, but it's a paid-for app. Do you want to hassle with sending them a check every month (let's say it's not doing very well, and you have to bother doing accounting and check-writing for $2.85 every month.)
Etc.
In general, it's their app, they should take possession of it. I can think of no benefit and many downsides to you keeping the app. I can think of no downsides and only benefit to them owning it.
---
Separately, if your app is boilerplate and reusable code, you might want to work out the I.P. ownership. But that's a different issue.
--
A: Because it disturbs the logical flow of a message.
Q: Why is top posting a sloppy method of writing?
--
You received this message because you are subscribed to the Google Groups "iPhone Software Business" group.
To post to this group, send email to iphonesb@googlegroups.com.
To unsubscribe from this group, send email to iphonesb+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/iphonesb?hl=en.
Posts
