Bitshares UI supports Beet in long-term development

View this thread on: d.buzz | hive.blog | peakd.com | ecency.com
·@sc-steemit·
0.000 HBD
Bitshares UI supports Beet in long-term development
<center>
https://pay98.biz/blog/wp-content/uploads/2018/02/bitshares-logo.jpg
</center>

A recent addition to the family of Bitshares applications is the Bitshares Companion application, now called Beet. The app was initially drafted and by clockwork, which handed over the source for the Beet application to the community. 

The goal of Beet is to make it easier for third party applications to work on the bitshares network, without having to worry about handling the private keys on these applications. Beet will be the handler for signing the transactions, while the application using it can focus on usability and functionality.

The bitshares teams believes that Beet fits nicely under the current UI worker in long-term development. Beet development will for the moment be supported by the UI worker and agreed to compensate for the initial development as source was released to the community. The project manager of the UI worker will handle issues, assignments, compensations in the same way as the current UI repo works today. 

We see great potential of development for Bitshares applications with the addition of Beet. While Beet is still in very early alpha, having it compensated under the current UI worker will make development speed up, improving the ecosystem.

Beet Gihub Repo, https://github.com/bitshares/beet
@clockwork writes about Beet on [his page](https://steemit.com/beet/@clockwork/beet-the-bitshares-companion)

*Project Manager of Bitshares UI*
👍 , , , , , , , , , , , , , , , , , ,