What are the options for branching iOS projects?

Question

iOS

There is an application for the iPhone. You need to make a similar application for another client - different branding, partially different functionality .. but the core is common + web services. Percent 70% of the total.
What is the best way to organize it?
I read about targets / schemes. But I do not know if it will be possible to do without copy-paste.
I really need advice from people who are experienced in these matters.

Answer 1

As I understand it, you want something when you make some fixes in the so-called. "core", then it would change everywhere. In general, the MVC approach is great for this. If everything is done correctly, the business logic is almost the same, and the interface does not change much, then the model and controllers can be completely shared, and if necessary, you can add some base classes for views.
The most obvious way for me is to shove it all into a framework and that's it. This is also convenient because everything except public headers will be hidden inside. You can make a beautiful encapsulation with a convenient interface outside. If something needs to be changed / added exclusive, then we simply inherit or make a category.
Another option is workspaces. I have never used it myself, but I know that you can add another project to one project (just by drag and drop), so that your base project can be used like that. Change something in the base - the changes will affect all projects that use it.