---
# System prepended metadata

title: Recent Projects

---

# Recent Projects


## Proto([https://www.proto.cx/](https://www.proto.cx/))

**About the project:** Our team has been working with their team for the last 7 months to customize their frontend application (Built-in vue.js), here we added new features and redesigned the whole system. The application serves as a frontend to manage their AI-based chatbots where users can use the drag-drop option to customize the bots behaviors, we updated and added new features to the bot management interface and redesigned the whole interface in general. For the last few months, we have been working on the track cases features, by using chatbots people can fire cases and allow the managers to see them through the dashboard. The application also includes mapping capabilities and analytics.

**Technologies used:** Javascript in vue.js framework, Docker, GitLab pipelines, amazon web services,...

**Process:** We work closely with the client, where we share on a daily basis with their tech team the update on what has been done, through the scrum methodology our team coordinates with their scrum master on how different tasks are handled along with the sprint planning. Our team here coordinates with Proto’s distributed QA test team to closely check if every developed feature matches the user’s expectations. The software also involves practices of automated testing and continuous deployment to both staging and production environments.


## Dacade ([https://dacade.org/](https://dacade.org/))

**About the project:** A decentralized e-learning platform, where learners are incentivized to build projects and cooperate. our team is in charge of developing the whole application and maintaining it.

**Technologies used:** Javascript in vue.js framework, netlify, and Github pipelines.

**Process:** We work closely with the client, where we share status updates on a weekly basis and we plan 2 weeks time sprints where we also involve the client in the planning. The project is built using different continuous deployment practices including automated testing and automatic staging environments deployments. Our team QA test team is in charge of testing every feature we develop.


## Eventivize ([https://eventivize.co](https://eventivize.co))

**About the project:** A decentralized application which allows event attendees to support their favorite artist by giving them drops which are transferable into monetary value, all this is done using blockchain making the application decentralized and transparent . Our team is in charge of developing the frontend version of the application and integrating it with the blockchain.

**Technologies used:** Javascript in react.js framework, pwa, netlify, Cosmos sdk, ...

**Process:** We work closely with the client, where we share status updates on a weekly basis and we plan 2 weeks time sprints where we also involve the client in the planning. The project is built using different continuous deployment practices including automated testing and automatic staging environments deployments. Our team QA test team is in charge of testing every feature we develop.


## **Wahl-O-Mat**

**About the project:** It is one of the most popular election tools on the Web: the Wahl-O-Mat from the Federal Agency for Civic Education. In the run-up to the elections, the participating parties take a stand on different questions. Users vote on the same questions. The program then calculates which parties are closest to the user’s own political positions. Besides the classic orange-colored design, there are additional skins according to the occasion be it the elections to a state parliament, the federal German Parliament, or the European Parliament. The success of the election tool has grown steadily over the last few years.

Our team is in charge of developing the ios and android apps which will be used in the next Bundestag election of 2021.

**Technologies used:** Javascript in vue.js framework, netlify, and Github pipelines.

**Process:** We work closely with the client, where we share status updates on a weekly basis and we plan 2 weeks time sprints where we also involve the client in the planning. The project is built using different continuous deployment practices including automated testing and automatic staging environments deployments. Our team QA test team is in charge of testing every feature 

we develop


## **Chapping**

**About the project:** A peer to peer video calling app which uses the power of [WebRtc](https://webrtc.org/) to create seamless communication between users and adds functionalities on top of classic video calling features by consuming external APIs and shares the data among the call attendees. 

Our team is responsible for the whole development of the application from web applications to mobile apps.

**Technologies used:** Javascript in react.js framework, PWA, netlify, express.js, webrtc, WebSockets, peer to peer servers(peer.js),...

**Process:** We work closely with the client, where we share status updates on a weekly basis and we plan 2 weeks time sprints where we also involve the client in the planning. The project is built using different continuous deployment practices including automated testing and automatic staging environments deployments. Our team QA test team is in charge of testing every feature we develop.


## **BigBlueButton Proxy server**

**About the project:** Our team worked on the project to deliver a unique solution that allows the open-source video calling app** BigBlueButton, **to have multiple secret keys thus also adding an option to manage multiple clients and BigBlueButton servers. The application acts as a gateway for applications that want to connect to BigBlueButton servers. The application receives the client keys and links them to the appropriate servers if their client’s keys are valid. This brought an option to grant and revoke access to clients applications without affecting all clients using the same server

**Technologies used:** Ruby on Rails, Postgres

**Process used:** Since the project started off as a prototype, we involved the client in the decision making as the project was taking a different path than what was originally expected. We planned 2 weeks time sprints where we would go through the project with the client and observe the current changes and what was next for the project. The project also involved continuous deployment techniques which would allow the client to view the progress in real-time.
