Get Support for WAT
Use http://wat.codeplex.com for all support and issue logging
Managing changes to your website
One of the advantages of using WAT is that you can update the underlying website when you need to and the app will get updated instantly. The reason for this is because WAT apps are a wrapper around your live site so changes are reflected immediately.
However, there are some areas in the WAT configuration that are hard coded into files like config.json or one of the several CSS files. Because these files are part of the native app, if they to be changed, the app will have to go through store certification again as an update (can take up to 7 days, but is typically less than 24 hours for updates).
These are some of the common updates to websites that will require your native app files to be updated and therefore the app to be re-submitted to store:
- Changes to your URLs: App bar, nav bar and settings links are hard-coded in the JSON file. This means that if the URLs change on your site, the JSON will need to be updated accordingly and the app will need to be re-submitted. A workaround here is to implement 302 redirects on your web server (this is good practice for SEO anyway).
- New/removed navigation links: App bar, nav bar and settings links are hard-coded in the JSON file. This means that if you need to add or remove links (for example, seasonal promotions, sales etc.), the JSON will need to be updated and the app will need to be re-certified.
- Changes to HTML class names or ID’s: One of the most powerful features of WAT is the ability to inject CSS to override the styles that comes from the site. This feature relies on using either the HTML element ID or CSS class name. Therefore, if any ID or class name is changed on your site and the injected-styles.css file overrides it, then the inected-styles.css will need to be updated and the app will need to be re-submitted.
- Any changes to your JSON: Some of the examples above are common areas that will require app re-certification. However, any changes to the native files in your app (config.json or *.css) will need app re-submission. Therefore it is important that when your website does change, the app config and styles are reviewed as part of the test process for your site. If you know that you are going to make breaking changes to the site, make sure you submit an update to your app at the same time.