This is a general question and I'd like to hear if my approach should be used or not.
At the Appway Conference I was told that no bookmarks can be created for sites displayed on the Developer Portal. I now decided to use a function out of the HTML5 API, namely history.pushState(). Process Instance URLs can be replaced without having the browser requesting the new URL from the webserver. If a user proceeds to another site / link an clicks their browser back button, the newly set URL will be requested instead of the previously replaced URL of the process instance.
Therefore, bookmarks can be created and links can be shared. However since this is quite a new API, not all browsers support it (see image). Furthermore, it's rather a workaround instead of a solution I'd propose as a best practice.
What do you think about this (especially R&D and UI guys) ?
At the Appway Conference I was told that no bookmarks can be created for sites displayed on the Developer Portal. I now decided to use a function out of the HTML5 API, namely history.pushState(). Process Instance URLs can be replaced without having the browser requesting the new URL from the webserver. If a user proceeds to another site / link an clicks their browser back button, the newly set URL will be requested instead of the previously replaced URL of the process instance.
Therefore, bookmarks can be created and links can be shared. However since this is quite a new API, not all browsers support it (see image). Furthermore, it's rather a workaround instead of a solution I'd propose as a best practice.
What do you think about this (especially R&D and UI guys) ?