This article was first published on Stories by Augur on Medium
Augur Weekly Report — February 13th
Over the past few weeks the developers for Augur have been re-organizing around three major initiatives.
- Designing new UI concepts that will be added to our Reference UI. These changes are taking into account a lot of feedback we’ve gotten about the usability of various features of this UI, and begin to establish best practices for communicating complex information to users. Many of these changes will be integrated into the current V1 release and will be usable with the current contracts.
- Implementing the new UI designs beginning with a new Trading interface, and now expanding into a redesigned Portfolio page which will make it much easier to understand what shares a user holds, as well as the states of the markets in which a user is participating. We’ve broken out tasks for each of these three major pages, and will be scheduling their development over the next four weeks. Pipelined with this developers are creating re-usable components that simplify building new UIs with the goal of having them be re-usable both within our reference UI, but to simplify third party developers building UIs that can speak to the Augur contracts.
- The backend team is working hard on very exciting developments with the Augur V2 contracts. These contracts have been successfully changed to support using DAI (technically, any ERC-20/777 token) as collateral. These changes come along with a myriad of internal changes to our testing infrastructure for contracts. Backend development is now well underway for a new concept for Augur Node, which is a fully in-browser solution for supporting the UI. This new code is in its early stages but developers have been concentrating on how to speed up synchronization, how to keep all state within a browser session, and how to maintain reliability through reorgs ...
To keep reading, please go to the original article at:
Stories by Augur on Medium