In this update we talk about goals for the legacy CanWork codebase & development of the decentralised architecture.

What’s happened since the last update?

Since the last update, the team held strategy planning sessions for CanYa’s engineering team goals, continued to support CanWork.io and integrated Dock.io into our ecosytem.

Sign in with Dock — decentralised login and account verification

Engineering Team Goals

The engineering team aims to achieve three key goals in line with overall organisational goals.

#1 CanWork “Business as Usual”

This goal provides continued support for the existing CanWork architecture and code repositories:

A stable and working application that freelancers can use

A testbed for decentralised features & architectural improvements

A reduction in change risk and regressions (test automation)

Minimise cloud compute & SaaS costs

Additional features based on user feedback. A reasonable back-log of these already exist. If you have any ideas for platform improvements please let us know viaTelegram or email.

The overall strategy is to keep the legacy code base alive until it can be superseded by a decentralised alternative, and keep manual intervention to a minimum.

BAU support

Address GitLab issues & bugs

Feature improvements targeted toward marketing & adoption

Stability, quality and test automation

#2 CanWork Decentralisation

This goal will continue research and development of a decentralised version of CanWork. Efforts include:

Tech spikes

Research & Development

Implementation (legacy code base)

Implementation (new code base)

We aim to release the finalised version of the decentralisation overview to the community in a dedicated tech blog in February.

#3 Community Developer Presence

We are now up against the cutting edge of what is possible with Ethereum and decentralised technology (for example we are currently waiting on the ETH dev community to release Constantinople so we can do our token swap to ERC 777). Therefore, an organisation goal for 2019 is to consistently keep the community informed and consulted about the tech direction of the platform.

To support this, the engineering team will assist with community management by providing a heightened level of technical blogs, code samples and social media content.

What’s planned for the first sprint ?

The development team will use an agile sprint format similar to our previous operations with the notable difference of 3 week sprint cycle.

In this first sprint starting 28th January, the dev team expects to address CanWork ‘adoption’ features, SEO, and improvements in line with CanWork Legacy goals. Specifically,

Email on-boarding and retention. This will provide a better on-boarding flow for new sign-ups while better notifying and engaging existing users.

This will provide a better on-boarding flow for new sign-ups while better notifying and engaging existing users. Planning & business analysis for a financially incentivised referral mechanism for CanWork

for CanWork Setting up the blog sub domain for CanWork tutorials & content. This will help with SEO and act as a resource repository for our users. Tutorials will also be added intuitively throughout the onboard and workflow processes.

for CanWork tutorials & content. This will help with SEO and act as a resource repository for our users. Tutorials will also be added intuitively throughout the onboard and workflow processes. Begin migration of content from Medium (SEO)

from Medium (SEO) Refactor some legacy code to improve stability and reduce cloud costs on the transaction monitor

In addition, we will begin the tech spikes on peer-to-peer (p2p) chat & video conferencing in line with CanWork Decentralisation goals.

Join the Telegram discussions!

Please join our CanYa Telegram Channel for interim updates, or come chat to the CanYa team and community.

Links: