# Runtime versus Design Mode
FON can be used in 2 quite different modes. 


    ### Runtime Mode

    In runtime mode you deploy the FON web application with your Camel routes and application services; then you can use FON to view and edit your routes at runtime, browse endpoints, create endpoints, send messages to endpoints and browse messages on some browsable endpoints (like file or JMS queue endpoints). 

    Saving a route in Runtime mode stops the currently active route (if there is one), removes it, then adds the new route and starts it. Other running routes are left untouched. This lets you add new routes into a production system to perform diagnostics for example.

    ### Design Mode

    In design mode you are working directly with source code before you build and deploy your application. For example you might want to use FON to view and edit some Camel routes as part of your development process; then after you have finished editing the routes you perform a build process using a tool like Maven to create some artefact (jar, bundle, war etc) which will be deployed into an application server later on.

    Saving a route in Design Mode will just replace the **camelContext**; element within the Spring XML file you edit. Note that all content above and below the **camelContext** are preserved - though any comments inside the **camelContext**element will be discarded.
