# Running the App (Web Browser)

***These steps are common to all 3 apps in this platform. You will be redirected to this section again, if you skip this initially.***

### Install the app dependencies

After you have Ionic installed, you have to install all the dependencies required by the app. These dependencies are listed in `package.json` file in the root of the project.&#x20;

To do this  :

Open your favourite code editor and open the app folder which is **ION-4-TAXI-USR-FB-ionic5** in this case. It should show the following files.&#x20;

![](/files/-M5CV7WAPIhNsgc0_hQw)

Now open a terminal and make sure that your folder name is shown at the terminal to ensure that you are running the following commands inside your ionic app folder path.

Run the following command

```
ION-4-TAXI-USR-FB-ionic5 $ npm install
```

The screen with the **npm install** running at the VS Code terminal is shown below.

![](/files/-M5CVe0WZxezypmVHgXz)

If you are using latest NPM, you might see an audit report after the installation is completed. If you see any vulnerability marked as `high` , please contact us regarding the same.

###

### Run the app on Browser

Make sure you have the [initial setup](/ionic-taxi-booking-app-starter/setup-and-deployment-1/initial-setup.md) done, before you try to run your app.&#x20;

First we'll run the app in development environment.&#x20;

In development environment, your app runs in a browser (of your choice).&#x20;

It is recommended to make all changes and development while running the app on browser . Running on device while developing will be too time consuming.

After completing the above step we will run the app on browser, run the following command

```
ION-4-TAXI-USR-FB-ionic5 $ ionic serve
```

The screen with the "ionic serve" running at the VS Code terminal is shown below.

![](/files/-M5CW6V9MsJmsYN3vx79)

Make sure that your folder name is shown at the terminal to ensure that you are running the following commands inside your ionic app folder path.

This will build the project and deploy it on a `localhost` url (usually it is `localhost:8100`).

The initial deploy process will take some time when it creates "chunks" of code pieces. Once you see `compiled successfully` , you are good to go.&#x20;

After successfully running the app, your browser window will open automatically and load the app in a full screen view, as shown below.&#x20;

![](/files/-M5CWOPg4lrBg8lzHkpD)

To change the app to a device view, right click anywhere on the browser and choose `Inspect Element`and choose device mode.

The screen running the app in **device** **mode** is shown below.

![](/files/-M5CX51OFJxez9EaDm0s)

{% hint style="success" %}
If you are running both User and Driver apps together on same browser to test booking flow, make sure you run them in separate windows, and clear stored cache before trying to login. Otherwise User Firebase credential can login the Driver app, and vice versa. This can confuse the apps between roles.
{% endhint %}

More about browser development tools can be found out in following links

* [Chrome Dev Tools](https://developers.google.com/web/tools/chrome-devtools/device-mode/)
* [Firefox Dev Tools](https://developer.mozilla.org/en-US/docs/Tools)

## Next steps

For Complete Integration of These App checkout the Section  [Taxi Booking Complete Setup](/ionic-taxi-booking-app-starter/how-to-use-this-starter/taxi-booking-complete-demo.md).<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://enappd.gitbook.io/ionic-taxi-booking-app-starter/setup-and-deployment-1/running-the-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
