Web development

Web application development starts with specifications and design analysis required to build the right architecture. It is the architecture where the future scalability of the entire application is set.

Choosing the right technology stack early in the process is critical. The planning starts with the correct server infrastructure to various frameworks/libraries and databases.

Our team has a wide range of competencies, which allows us to competently advise the client on the technology that is best suited specifically for his product.

We have internal developments and starter-kits allowing us to speed up the process of creating web applications as well as our own guidelines for unifying and reusing code within the project.

The front end is how a product looks and feels. It is through the front end that the user interacts with the application. It is extremely important that the interface is displayed and functions well on every possible device and any screen resolution.

When building a front-end architecture, we use the component-based approach. This allows us to reuse interface elements and their behavior logic within the application.

The loading and functioning speed of the interface matters — we use all the latest trends and techniques for optimizing and caching web applications, thus providing customers with the best possible experience of interaction with the product.

The back end is the “brain” and the “memory” of your application. It is the logic and the computation within your application, as well as working with data.

The back end usually consists of a web server, a database, and an API - a commuting way between the back end and the client-side of the application.

We care about data security and encryption. We apply the common cyber attacks protection methods when building the back end.

We build the architecture as a solid and efficient base. We utilize various types of Unit as well as load testing to get the app ready for high traffic and ensure stable functioning in high-pressure conditions.

No matter the type of platform you choose for your product, we can help you develop a scalable, reliable, and secure back end.

The correct workflow setup allows distributing resources in the best possible way. It also helps to keep abreast of the progress.

Our team has a clear Git Flow that allows developers to work on tasks independently. We practice code reviews to optimize resources and minimize the chances of bugs before the QA stage.

We prefer to use GitHub for the collaborative development process. We use Asana/Jira for task management and triage.

Each product is unique in its own way. Therefore, we choose Scrum, Kanban, and TDD methodologies depending on the project.

We only use the fastest servers with 99.99% uptime and optimal resource scalability.

Solutions from DigitalOcean, AWS, Google CloudPlatform, and Heroku are used the most often in our workflow, depending on the needs of the product. We assign a dedicated DevOps expert for server infrastructure configuration and maintenance for every project.

We configure Continuous Integration and Continuous Delivery (CI/CD) to run automated builds and tests after the new code has been merged into production, and to deliver files to the test server. This allows us to spot issues and test the app’s performance on the cloud server before launching it into release.

Authorization is an essential part of modern applications, regardless of the platform.

We know and are able to implement authentication both ways: using third party services (Auth0, Firebase, AWS Cognito, etc), or we can implement it ourselves from scratch.

We also have experience implementing two-factor authentication.

We know the algorithms of JWT tokens, which allows us to easily create our own solutions and securely store/update tokens on the client-side. Auth tokens are stored encrypted in browser memory and HttpOnly SameSite cookie. It was created by the server to avoid XSS and CSRF attacks. This approach allows us to authenticate the user during Server-side rendering even before the first load of the application.

We fully realize the responsibility to the client and the end-users when creating a product.

Therefore, we set aside time for writing Automated tests and Manual testing when creating new functionality. Investing time in writing autotests helps to improve the stability of the service and find possible bugs and conflicts quickly when scaling a project.

We select the most appropriate testing types based on the needs of the product. We resort to the following four most often:

1. End to End method. An assisting robot, copying a user’s behavior, clicks around the application verifying its proper performance.
2. Unit method. It includes verification of the units’ anticipated way of functioning
3. The integration method includes verification of various units working together coherently
4. The so-called static method implies catching typos as one writes code

When developing a product, one often has to integrate it with other services and applications: analytics, payment processing software, live chat, CRM system, etc. These services can help to launch your product faster, get more data on your customers, and improve your marketing strategy.

We have experience with API integrations for the most common services so we don't spend hours studying records and documentation. Here is a list of APIs we’ve dealt with: Google Analytics API, Segment API, Google Drive API (Docs, Sheets, etc), Google Maps API, Amazon API, HubSpot, Intercom, MailChimp, SendGrid, Telegram, Slack, Stripe, Auth0 API, Instagram API, and many more.

Thanks to our experience with third-party APIs (and writing our own), we quickly deal with the integration of various services and use the client's resources efficiently.

We build lasting partnerships with every client. That's why there is no such thing for us as the “Final release”.

We provide lifetime support to our projects in order to constantly improve its quality and introduce new functionality.

Within this collaboration format, we monitor the use of the latest versions of packages and libraries and support the Cloud Infrastructure of the project.

If you decide to transfer the project to your internal team, we will prepare the supporting documentation and consult the new team for a fast project introduction.