What are some general guidelines for setting up an iOS project I will want to personally publish but sell in the future?

Posted by RLH on Programmers See other posts from Programmers or by RLH
Published on 2012-09-12T13:31:51Z Indexed on 2012/09/12 15:49 UTC
Read the original article Hit count: 279

I have an idea for a personal iOS project that I would like to write and release to the iOS store. I'm the type of developer who enjoys developing and publishing. I want to write quality software and take care of my customers. Assuming that I wrote an application that had reasonable success, there is a fair chance that I would want to sell the ownership rights of the app to another party and I'd use the proceeds to develop my next personal project which, in turn, I'd probably want to sell in the future.

With that said, what are some general guidelines for creating, making and publishing an iOS project that I will eventually want to transfer to another company/developer?

I know this is a bit of a broad question, but I request that the given advice be a general list of tips, suggestions and pitfalls to avoid. If any particular bullet point on your list needs more explanation, I'll either search for the answer or post a new question specific to that requirement.

Thank you!

Note Regarding this Question

I am posting this question on Programmers.SO because I think that this is an issue of software architecting, seeking advice for setting a new application project and publishing a project to the Apple iOS store-- all within the requirements for questions on this site.

© Programmers or respective owner

Related posts about design

Related posts about project-management