We’re excited to share with you details about our development processes, the platform progress made thus far and how we organize our work internally. In this article we will briefly go through some of the topics which we think are important for delivering a scalable next gen automated job platform.
Highlights
- Golden Circle, Buyer Personas, Brand Attributes
- UML class diagrams and ERDs
- CI/CD and code quality
- Blockchain microservice to communicate with Matic Network
Golden Circle, Buyer Personas, Brand Identity
The Golden Circle played a pivotal role at the very beginning while we were still defining our product requirements and functionalities. By answering the three main questions — “What, How, Why”, we were able to visualize and define our value proposition.
The Golden Circle was quite helpful, but we didn’t stop there. We wanted to take a step back and make a more thorough analysis. We began by defining a detailed Buyer Personas of our potential clients. This helped us to figure out and pinpoint the problems that they often encountered. Thus, we defined a clear and customer focused Brand Strategy, identifying our brand attributes, company goals and the target customers. Full details can be found here
Once our target customer have been determined, we proceeded to shape our Brand identity, Brand attributes and the whole UI/UX corporate design. Based on the stylescapes, we made final decisions regarding the visual direction of Ispolink’s identity. We managed to setup the final visual language, created multiple logo ideas, color palettes, typography and many other brand assets.
It was essential for us to provide a personalized UI/UX tailored meet our customer needs and make the entire user experience seamless.
Here are a few excerpts of mockups showcasing our product progress:
UML Class Diagrams and ERDs
Defining a robust architecture is crucial for complex platforms like Ispolink.
Once a detailed specification for all features of Ispolink has been made, we began to reason about the architecture and how to make all modules and entities flexible enough to guarantee the scale that we want to achieve. After a few brainstorming sessions and lots hard work we had all diagrams in place.
CI/CD and code quality
At Ispolink, we highly value the quality of the code written and also make sure to utilize the best established practices. That’s why each internal project has a CI/CD pipeline which runs a set of automated unit and integration tests. This helps us catch bugs early on and guarantees the reliability of the platform.
Additionally, this allows us to quickly integrate changes on test and production as soon as somebody merges a PR. We don’t need to manually manage deployments, everything is automated.
Blockchain microservice to communicate with Matic Network
For the past few months we have been working closely with Matic Network to ensure that we can reliably accommodate fast and cheap in-platform crypto payments. We began working on the integration of our token while Matic Network was still in Beta. There were a few hurdles related to the withdrawal that we’ve experienced, but with the help of Matic’s core team we were able to quickly resolve those issues.
Our Matic microservice contains full documentation along with API specification. It runs on our test environment along with ETH node.
Stay in touch with us for more updates.
Website: https://ispolink.com/
Whitepaper: https://ispolink.com/Ispolink_Whitepaper_v1.pdf
Linkedin: https://www.linkedin.com/company/42473350
Twitter: https://twitter.com/ispolink
Email: contact@ispolink.com
