Let's develop your idea together!

The brief is the foundation of any successful project. It defines the customer’s vision, helps to create clear objectives and ensures that everyone is on the same page.

The brief is a short 1-3 page document which describes the main goals for the project.

As well, the brief should include a targeted audience: people who will use the launched project.

The brief is usually created by the Project manager in close communication with the customer.

One of the best options to gain insights while starting a project is prototyping.

It includes producing an early, inexpensive, and scaled down version of the product in order to find any hidden requests and problems for the future design phase.

Prototyping helps you and the designer to bring ideas to life, test user experience while using the future product.

Need to remember, that prototype is not the final product. No need to expect a fidelity or pixel perfect solution, it’s just quickly to test your idea and after to proceed with design. On the other hand, exactly at this step you need to validate the flow for future web application, as defined structure at this step will be used for design and development after.

The design is what creates the whole look and feel of your website. It’s the process of building the user experience and user interface.

The designer works with layout of images, fonts, colors, styles, graphics, animations and so on. These elements define a website or app look, how it will work on different devices, what users will pass on all pages or screens.

The designer as well defines all properties for future development and helps to reduce time for further application creation.

A specification - is a document that includes objectives for developing the application, constraints for it, technical requirements. But the main idea to remember, that the specification each time is different for each project, as all projects are unique.

For example, one project might require design and development, but another project might build only for SEO optimization.

However, there are some sections that can be re-used for almost all web projects. You can check them in the attached example.

Web development can be divided into two broad divisions - front-end development (the content, design and how you interact with it on the website) and back-end development (controls what goes on behind the scenes of a web application).

Frontend developers mainly use HTML, CSS and JavaScript for displaying all content of the website. In Pixeleez we use as well frameworks as such:

• React
• Vue.js
• Angular

Backend developers can use many different coding languages and frameworks. In Pixeleez we use:

• Ruby on Rails
• Python
• PHP

Quality Assurance engineers, known as QAs, focus on preventing defects (also known as bugs) in the project.

They test on each project iteration all possible deliverables.

On planning, QAs can check whether all requirements are identified and taken into account.

On development QAs test whether a developed solution is possible to use and it’s understandable in usage.

Before release, QAs tests whether all project functionalities work smoothly together.

Thus quality assurance is the process of preventing quality issues in any project.

Pre-production (known as well as staging or UAT) is a copy of the production website on a private server. This is the safe place where you can test all your developed functionality, any changes and not be scared to make an impact on your live website.

Pre-production isn’t crawled by Google and you can be calm that all basic Internet users won’t find it by simple search.

Hooray! Your project passed all development iterations and now it’s ready to be presented to the whole world.

Release means that the project is released in a production environment where Google can crawl it and all Internet users can find it by simple search in the browser.

Some projects can have releases even each week, if the updates go live constantly and the project is organised in 2-3 weeks iterations.