We do our best to make working with us easy and enjoyable for you!
We realize how precious your time is and we respect that
For over 5 years, we’ve been using a method that works like magic and saves a considerable amount of your time. This method is amazing as it allows you resolve upcoming issues step-by-step and gives enough time to think. You work with us at the time you prefer and you’re not bound by any scheduled meetings, and it really simplifies our communication process.
Discuss details in writing
Create project
Approve wireframes
Our development methodology
(scrum inspired)
Learn more
Finish project on time and within budget
Our team is open for interesting and challenging projects
Let’s see how it works in detail

We typically use Skype and Google Docs as communication tools.

Communication is done in writing and this gives you a big advantage.

First of all, this ensures that no single idea, feature or promise will be lost or forgotten about. You can always rely on the chat history and refer to it, if needs be.

Another big advantage is the opportunity of replying to us at any convenient time for you.

You don’t have to make appointments to talk to us as we’re always available online.

We use Skype to discuss and resolve smaller issues, but all dones and to-dos will be saved in a Google Doc.

This is also the place where we keep all related project data, such as credentials, links to wireframes, mockups, etc. You will also have the complete structure of your project and the possibility to keep track of the progress.

We love complex projects.
If others think your task is too complicated for them, we’ll handle it
Wireframes and Mockups won't be your headache any more
We use mockflow.com for wireframes and maquetter.com for mockups, which makes it easy to view and approve designs for you. These wonderful services allow you to work with mockups and wireframes online. You can view them there, approve them and make comments. We discuss your suggestions in Google docs and then make changes. At this point, it’s very important not to be in a hurry as you are building the fundamentals of what your website will look like in the future. This method allows you to take your time and think through even the tiniest of details.
Our development methodology
(scrum inspired)

We use Design by Contract (DbC) approach to develop our projects. In simple words means that the project is a split into several parts (milestones) and every milestone represents as an independent functional block. It is close by meaning to potentially shippable increment term used in Scrum.

Once we have a complete project structure and very detailed wireframes we split project into milestones. Each milestone is estimated separately in hours needed for its development and can take around 2 weeks to be implemented. In the end client gets the complete functional block.

Let’s see in detail how we work
at a single milestone.

In the first week of the current milestone designer develops mockups, lead developer writes documentation in RAML format for that part of REST API which we are going to build in this milestone and QA engineer writes test cases which cover functionality from this milestone. After mockups was approved by client frontend developer starts with slicing mockups into HTML/CSS. In the second week a group of backend/frontend developers starts implementing functionality from the milestone. At this moment they already have RAML documentation for the REST API which regulates client-server communications and HTML/CSS for the UI. After server side and client side code was finished QA engineer starts verification of the functionality from the milestone using previously written test cases. If there are any bugs found by QA engineer, backend and/or frontend developers immediately fix them. When all test cases passed successfully milestone is considered to be finished.

In the second week the first group starts already working on the next milestone. In this way we ensure iterable parallelized development process which is easy to control and allows to detect flaws in initial design on the earliest stage of development.

We used this methodology approach on different projects, both smaller ones (3-4 months) and bigger ones (>12 months). It proved to be efficient for all sizes of projects. This approach allows everyone to stay focused on a small functional block and to keep in mind all the tiniest details related to this block. Unlike classical development processes, such as Waterfall or RUP, iterative approach makes it possible to make changes to functionality at any time. If something needs to be changed, we update wireframes firstly. Then we check what milestones will be affected by this change. If functionality that is already implemented needs to be modified, we create a new milestone to make the necessary changes. If the milestone has not been implemented yet, we will make changes to it at once and then keep them in mind when we start development of the functionality in this milestone.

One milestone includes:
RAML documentation development
Wireframes development and online approval
Development of Test Cases
Frontend development
Backend development
Admin panel development
Testing using developed Test Cases
Bug fixing