API and XAMARIN project

Asked

Viewed 43 times

1

Guys I have a Solution where to stand all the architecture to display my API. The project that will consume this API will be in XAMARIN. My question is: I must create within the Solution this project or in another Solution?

I believe that in the future other people will develop in Xamarin and did not want other people to have access to the structure of the API project.

Is there any other solution to this?

1 answer

1


Well, you’ve answered your own question.

Create another solution for the project in Xamarin, which most likely will have nothing to reuse from your API. The only thing he should do is consume services that are being exposed by her publicly, as well as any other client application may also do so (if this is within her plans).

Here are some reasons that reinforce the fact that the client project (in this case in Xamarin) should be in another solution:

  • It will not be reused code from your current solution, since they must have different natures, objectives and maybe even distinct scopes;
  • Your API services and the Xamarin project follow completely different and not necessarily related evolutionary lines;
  • As you have already reported, it will be different teams that will handle each of the solutions;
  • It would be an unnecessary exposure of one project’s resources on the other, littering the development in your IDE;
  • Even if possible, it is very unlikely that you will want to run both projects (api and app) so that they are communicating during development/testing.

I hope I’ve helped.

  • Thanks for the clarification. I needed these reasons to be able to remedy the doubt.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.