AndyDark
Well-known member
Hi everyone,
I'm Andy Freer and currently leading the Evolution web/mobile development team and reporting to Evan.
I thought I would give some background on the Evo development and a (very) brief update as to where we are for those who are interested.
Team structure
Our team is designing & developing DAPI and everything exterior to that, such as the API libraries, Evo wallets, client libraries, SDKs, usage samples, documentation and also the ecosystem components to communicate & provide that when Evo is launched, and the team is currently segmented between Web and Mobile contributors.
The core layers of Evolution such as DashDrive and DAPI internals are being developed by the core team so it's a collaboration between teams with DAPI being the touch point we interoperate via, with Evan guiding the overall system architecture & development.
Development Status
We have mapped out the full top-level Evo architecture now and have prototypes / proofs of concept code for most of the areas we need (which are mainly Dash Social, Dash Wallet and Dash Pay).
The next step will be organizing and integrating some of these projects into the full suite of repositories we need, along with finalizing some of finer details of how some of the components will operate and interoperate, and speccing everything.
So we are still in essentially design/prototype phase but soon we will be full-swing into the development phase and it will get easier to communicate what the progress is and enable contributors to work more productively.
Questions
If there are any questions you have that are in our team's area me or one of the other team members can try to answer it here. I don't think many team members are big forum users as we spend most of our time communicating about development on Slack so apologies if answers are delayed or posts are missed.
I'm Andy Freer and currently leading the Evolution web/mobile development team and reporting to Evan.
I thought I would give some background on the Evo development and a (very) brief update as to where we are for those who are interested.
Team structure
Our team is designing & developing DAPI and everything exterior to that, such as the API libraries, Evo wallets, client libraries, SDKs, usage samples, documentation and also the ecosystem components to communicate & provide that when Evo is launched, and the team is currently segmented between Web and Mobile contributors.
The core layers of Evolution such as DashDrive and DAPI internals are being developed by the core team so it's a collaboration between teams with DAPI being the touch point we interoperate via, with Evan guiding the overall system architecture & development.
Development Status
We have mapped out the full top-level Evo architecture now and have prototypes / proofs of concept code for most of the areas we need (which are mainly Dash Social, Dash Wallet and Dash Pay).
The next step will be organizing and integrating some of these projects into the full suite of repositories we need, along with finalizing some of finer details of how some of the components will operate and interoperate, and speccing everything.
So we are still in essentially design/prototype phase but soon we will be full-swing into the development phase and it will get easier to communicate what the progress is and enable contributors to work more productively.
Questions
If there are any questions you have that are in our team's area me or one of the other team members can try to answer it here. I don't think many team members are big forum users as we spend most of our time communicating about development on Slack so apologies if answers are delayed or posts are missed.
Last edited by a moderator: