Recently, I started looking into building server to handle HTTP requests and user authentication with ASP.NET Web API 2. I aimed at allowing my mobile client, which is built with PhoneGap, to interact with my ASP.NET server.

I followed several guides found on the web and these sample projects could be built successfully. However, every tutorial I found always included web pages in the ASP.NET project. I really want to know if it is viable to have my web pages solely stored in the client, so the server can just act as a data provider and authenticator only.

Here is a common scenario I can think of:

```
1. app sends a GET request to retrieve a list of items
2. server receives this GET request
3. server queries the DB and retrieves a list of items
4. server serializes the list as a JSON object and send it back to the app
5. app receives the list of items and updates the page with the new data

```

If the previous architecture is not viable, that means I will need to have web pages included in the server project and be compiled together with the core logic code. Is this statement correct?