As explained in the July 12th Update, the Dev Team is working on both the live version of Boardwalk (V1) as well as the production version of Boardwalk (V2).

Boardwalk V2

There is a discernible method to how the production version of Boardwalk (V2) is being developed. First, the overall user story is considered. In Boardwalk, the overall user story includes all navigational actions one must take in order to view, request, respond to, and complete a deal. Then, after the story has been converted from a collection of drawings into a clickthrough model by @faffy, it is divided into story segments and developed from there.

The Wiki for the production version of Boardwalk can be found here, and it describes the entire process of V2's development from organization and management, to a detailed description of each page in the user story. A table of contents exists on the right side of the Wiki. Under the “Site” header, each story segment is listed as a subheader, as well as a list of elements involved in this story segment. If you click on any list links, you will get an in-depth explanation of each page or element.

The story segments are being worked on sequentially, so in this case “Entry” is first. @bkawk and @kikipluche are responsible for creating the Wiki article so that what will be built is clearly explained before production begins. Then @xardas and @bkawk build the visual layer of each page (HTML and CSS) before element functionalities are added; for instance the ability to crop the Avatar picture, and scanning a QR code.

The Dev Team believes that in the interest of saving resources, it’s good practice to make sure the entire first story segment is functioning perfectly before moving on to the next one. The reason why this is important is the underlying code base and file structure gets reused in subsequent story segments, so if that is correct it becomes a foundational element that can be built upon. The Dev Team can then move forward without worrying that they will need to revisit the foundational code.

To that end, the “Entry” story segment gets thoroughly tested. For instance the Dev Team must verify the segment functions properly on a wide variety of devices, operating systems, and browsers. In order to streamline this process, @kikipluche uses a tool called BrowserStack. BrowserStack visually simulates how the story segment performs on IOS, Windows, and Android devices and their browsers, and any errors get corrected before moving on to a new segment. The first segment most likely takes the longest to develop and test, but once completed the foundation has been set for the rest of the story.

Connect With The Dev Team

The Dev Team is always on the lookout for other developers who want to get involved. If you have Polymer or Solidity experience feel free to reach out to #devhive on the Swarm City Slack. You can get a peek at the project by reviewing Github, here, or if you’d like to be involved in testing new releases, please join #testersignup on Slack and read the pinned post for instructions.

More to come soon. Cheers!