Caesium

Challenges

For every customer and freelancer that decide to use a marketplace for work, the essential factors in choosing these platforms are convenience, reliability and the amount of qualified workers with good feedback. Caesium is a platform where a customer, individual or a team can feel confident when hiring, managing and working on projects. When Caesium proposed Redwerk to continue developing the product, we were pleased to receive an opportunity to supplement our experience with this great startup and apply our skills in web development.

Our challenge was to bring to life the marketplace with the two types of users: customer and freelancer, each with its own set of options and the ability to sign up and authorize via social networks.

After registration, a customer can create a project, describe it, define deadlines and find a team depending on needed skillset. In Caesium skills should be displayed in the form of hashtags like #design, #development, #testing and so on. As in any freelance marketplace, we needed to create stats and leaderboards for finding the best executives on principle: the more confirmed skills and accomplished projects the higher chances to be on TOP.

The platform should also offer workflow functionality: freelancers can see the tasks, communicate with the customer, track the work via a built-in time tracking system, create invoices and receive payments. One more great ability that we needed to add in Caesium is to collaborate and create teams for working on big challenging projects.

Solution

Caesium was built with Laravel, Postgres and Firebase at the backend and Angular and SCSS at the frontend, so we continued to use these technologies for further development. As a prominent JavaScript development company, Redwerk used Angular to provide dynamic elements of the app interface. During the working process, we continued the development of the product and even fixed several functions that did not work correctly according to the design.

Our team also faced the issue with SEO abilities of pages that are loaded by JavaScript. It was because Google’s crawler does not process elements in Angular, so we found the way to solve it by using a proxy server that goes through the page content, make the HTML copy and displays static copies of the pages to Googlebot.