Bryden Wood - Save System API
After several team projects, I finally got to work on my own side project at Bryden Wood. The problem arose when we noticed how the design configurations cannot be shared or saved easily by the users. There was no process in which it allowed a user pick up from where another user left off. This became an issue for the long term sustainability of the web app design configurations going forward, which needed to be fixed.
The approach was to utilise away in order to create save states based on what the user has opened within the configuration, so objects/clusters and all the required menus and panels. The web API used here was the History API, with some JavaScript and JSON. The URL was key in being able to send and receive different states, which created one JSON object which was modified by users at will.
A prototype of the save system API was implemented. It allowed a user to send a URL to another user, which then opened up the required data from the URL. The system created a platform to share configurations, as well as save certain states on the fly which would help future meetings with clients. The URL would update from the link in the address bar or from the live commands of the user, therefore architected a new depth to the creation of design configurations.
Due to data protection and client privacy, the video and link shown is an open-source tool that represents an example of a design configuration created by Bryden Wood – this was used as an example video to demonstrate how the save system API can be useful