anchor.diff:  
   == Solution
   
  -We recommend you to follow the instructions in the next sections and create the application step by step.
  +We recommend that you follow the instructions in the next sections and create the application step by step.
   However, you can go right to the completed example.
   
   Clone the Git repository: `git clone https://github.com/jbossas/quarkus-quickstarts.git`, or download an https://github.com/jbossas/quarkus-quickstarts/archive/master.zip[archive].
  
positive.code: == Creating a frontend
  
  Now let's add a simple web page to interact with our `FruitResource`.
  Quarkus automatically serves static resources contained in the `META-INF/resources` directory.
  In the `src/main/resources/META-INF/resources` directory, add a `fruits.html` file with the content from this https://raw.githubusercontent.com/jbossas/quarkus-quickstarts/master/rest-json/src/main/resources/META-INF/resources/fruits.html[fruits.html] file in it.
  
  You can now interact with your REST service:
  
negative.code:  * open a browser to `http://localhost:8080/fruits.html`
   * add new fruits to the list via the form
  
  == Building a native image
  
  You can build a native image with the usual command `mvn package -Pnative`.
  
  Running it is as simple as executing `./target/rest-json-1.0-SNAPSHOT-runner`.
  
  You can then point your browser to `http://localhost:8080/fruits.html` and use your application.
  
  == About serialization
  
  The library we use to serialize Java objects to JSON documents is http://json-b.net/[JSON-B].
  It uses Java reflection to get the properties of an object and serialize them.
  
  Most likely, you have understood already that using native images requires you to register the usage of reflection.
  
  So far, we haven't registered any class, even not `Fruit`, for reflection usage.
  However everything is working fine.
  
  The fact is that Quarkus performs some magic when it is capable of inferring the serialized types from the REST methods.
  
  When you have the following REST method, it is fairly easy to determine that `Fruit` will be serialized:
  
  