API and XAMARIN project

Question

API and XAMARIN project

Navigation

#1 by (1 votes)

1

Personal I have a Solution where to be all the architecture for exposing my API. The project that will consume this API will be in XAMARIN. My question is: Should I create within the solution this project or 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?

visual-studio xamarin

asked by anonymous 21.07.2018 / 21:23

1 answer

Condition for table relationship in laravel Why does this error of name 'sys' is not defined?

score 1 · Accepted Answer

Well, you have already answered your question yourself.

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

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

No code will be reused for your current solution, since they should have natures, goals, and perhaps even different scopes;
The services of your API and the xamarin project follow completely different and not necessarily related evolutionary lines;
As you have already mentioned, there will be different teams that will handle each of the solutions;
It would be an unnecessary exposure of resources from one project to the next, filling 'developmental' garbage in your IDE;
Even though it is possible, it is very unlikely that you will want to run the two projects (api and app) so that they are communicating during the developments.

I hope I have helped.