How to organize web api for web and mobile calls?

Question

0.00/5 (No votes)

See more:

I have a web api serving as a backend for mobile and web application.How i can organize its controllers actions and models.So to make it easy to handle future work.
For example

1-Same controller and different action name for mobile and web for example

api/Customer/GetCustomer_web
api/Customer/GetCustomer_mobile

2-Same controller and same action but different parameter

api/Customer/GetCustomer?app=web
api/Customer/GetCustomer?app=mobile

3-Different Controller

api/Customer_web/GetCustomer
api/Customer_mobile/GetCustomer

4-Something else

Also whats the best practice

What I have tried:

Tried different techniques to implement mentioned in question but need the best practice to do this task.

Posted 1-Apr-17 7:09am

Member 9129971

Updated 2-Apr-17 11:21am

Add a Solution

Comments

Richard Deeming 4-Apr-17 12:08pm

Why do you need to return different data depending on the caller?

Member 9129971 4-Apr-17 14:00pm

the more clear word is viewmodel not data, I have different viewmodels for web and mobile for example some fields are shown in web but not shown in mobile , there are different views for both mobile and web , you would say for this i can just create method with some other name, but the problem is the api is built in such a way that if i create other methods then it would be a mess for maintanance , so i need a solution without losing any previous effort.

Richard Deeming 4-Apr-17 14:06pm

But which fields you do and do not display is a UI concern.

In MVVM terms, the data returned from the API is the model. You use a view-model in the front-end application to adapt that model to the view.

Member 9129971 4-Apr-17 14:51pm

yes the model for ex:for web we have model A having fields a,b,c,d and for mobile we have same model A having a,b (here c,d are null).

Richard Deeming 4-Apr-17 14:56pm

No. You have the same model for both. You use the view-model to decide which fields will and will not be shown, and to adapt the model to the view.

You wouldn't have separate database tables for "web customers" and "mobile customers"; so why have separate models for them?

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)