remembers everything, is responsible for everything and remains with you
with the further development of the project.
Terms of Reference and Prototypes
We interview the customer’s workgroup, collect briefs and communicate with the customer’s IT service. From this work, a technical assignment is born: the document on which the site will be submitted. We also render - draw interactive prototypes of the future site.
We start drawing the design with a mood map. This is a set of elements, styles, fonts: they are worked out and selected by our experts. They help evaluate the style of the future design.
In parallel, a team of analysts is studying competitor sites using exclusive technologies, such as eye-tracking ( what is it? ).
When the layouts are ready, we test them for compliance with the terms of reference and completeness of the drawing, and also we do the UI-kit: this is a set of auxiliary elements that are not obvious on the layouts. On the right is an example of such a layout.
Stack of tools: Figma, Sketch, Photoshop.
Development: normal, urgent and agile
Development is carried out on one of three methodologies:
The best franchise website is TopGun Barbershop .
Example: TopGun Barbershop site . Launched the project for 4 months.
— Urgent. Here the stages go in parallel, for example, having drawn only the main page of the site, we already give it to the layout. Or put half the layouts — start their implementation. Allows you to save time twice, but also costs 50-100% more expensive.
Example: Sistema Capital (“Sistema Sistema”) - parallel website development and personal account + parallel execution of work stages (2 and 3 months, respectively, for the site and LK).
Example: “Thank you from Sberbank” - 2 months of initial development and further gradual incorporation of new partners of the bank.
Integration of the site with 1C and other systems
An example of complex integration with 1C: ERP - holding site " Cable Alliance "
At this stage, we are working with the IT service of the Customer: we are developing an exchange API, designing data exchange channels. The result: a one- or two-way exchange with 1C, ERP, AXAPTA, SAP and another 20+ lesser-known accounting and automation systems.
Production: development scheme, version control, autotests.
In the process of writing the terms of reference, we form the scheme of site blocks with dependencies: this allows programming in stages, and also giving parallel tasks to programmers.
Using a version control system for a project, you can put several programmers at once, and their changes are easy to track. The same technology is used in further site support.
When you submit a project, we use both automatic and manual testing to provide for everything. Download a sample report about testing a site.
Support and maintenance
We have five testers in the state who check the work both manually and through automated tests. What is important, we do this not at the end of the entire project, but at the end of each weekly stage, which provides control over the time frame.
DevOps and highload
We have our own DevOps engineers: we will build the optimal update deployment scheme, configure the cluster, and conduct load testing. And after the launch of the project, we will provide 24/7 supervision.
What stand out
Transparency of development. Clients see Studio employees in our Intranet system and communicate with them directly. Agreements are fixed in tasks, information is not lost (unlike mail or phone).
Warranty period. We provide a termless guarantee for work, the specialists will give you free advice on the administration and further development of the project.
When are we most effective?
- the site is technically not complicated, but you need a "wow effect": complex animation or 3D
- the site is integrated with several systems at once, and not everyone has documentation
- on the site right now / there will be high loads (from 10,000 visitors per day) and everything should work quickly
- for a number of works, you need not only “hands”, but also “head”, that is, analytics and consulting