JS, HTML, CSS
Bitbucket / Github
50% of users leave sites after 3 seconds if it doesn’t load. We make sites lightning-fast and keep all users engaged.
- Sites should weight just a few KBs. We keep our code as simple as possible. No bloated libraries.
- World-class image optimisations. Sizes, compression, crops, etc.
- We use CDN wherever we can to reduce network latency. Sites should be equally fast in every part of the world.
- Only necessary stuff is loaded at launch, the rest is loaded when needed.
- Heavy backend optimisation.
We’re not particular fans of getting 2AM calls about site being broken. When we do 1 thing, it won’t break 2 others.
- The architecture of our code is crafted by very experienced senior developers.
- Do not use 3rd party libs from unreliable sources.
- Every line of code is reviewed by senior developers.
- Our code is as lean as possible. Less code, less bugs.
- We do storybooks for components. They allow to modify component and see all consequences of that change immediately. This approach let us spot most of the bugs during development stage.
- We test on real devices, not simulators. Desktops browsers, phones and tablets.
You got more users on mobile than on desktop. We focus on all devices equally.
- Every resolution and screen size is coded and tested with equal care.
- Performance testing allows us to measure how sites perform on weaker mobile devices.
- All the images and videos are mobile-friendly and load quickly even in bad network conditions.
We want to focus on building features, not lose time on fighting with servers, configuration, device incompatibilities etc. That’s why we standarise and automate our processes as much as possible.
- Automatic builds.
- Automatic deployment system.
- Automatic testing environments.
- We leverage Docker virtualization to work in the same environment no matter what devices developers use.
We build reusable components first and then compose pages from them. It allows us to make development time much faster.
- Component based approach promotes reusability which in turn decreases development time and increases stability.
- We create storybooks. Storybooks are special pages showing all use cases of single component. By modifying one thing we are sure we didn’t break another.