Website Design and Development

Our main work is done in PHP and JavaScript, but we also use other programs and programming languages depending on the project requirements. 

Get a quote for web design services

The way we approach website work depends on the project profile. The project type, as well as the project status, are the ones to give further directions to our work. Experience has taught us that is for the project benefit to have a few guidelines to anchor our work to be. We have defined our own approaches, based on the projects we have encountered so far and we are updating them as we develop new projects.

Define/clear up the brief

The take-off of a website project is very important and that's why we need to create a solid project brief. It's impetuous that we gather all the important information about the project in one place, so, later on, we'll be able to share with all the people involved. 

Plan the work ahead

It's important to have an overview of the work that needs to be done in order to reach the project's goals. We draw a project timeline, mark the milestones and create the sprints with the corresponding tasks. This can be updated as the work starts but it helps in having a first overview.

Map the user journeys

Whether the project is a ground-zero website or not, we need to define/review the user journeys. We need to know what the users will be doing on the website and what routes will they access to achieving their goals. When a project is more complex, personas might be needed to better map the user journeys.

Create structure with wire-frames

Once we gain knowledge about the user's goals, we can start drawing the structure of the website. We create 'wireframes', simple sketches illustrating the sections that we'll display on each page. We usually create a prototype with them, so everyone involved in the project forms an idea on how users will find information/interact with the interface.

Design layouts

At this stage, the prototype of the wireframes has reached everyone involved in the project and has been debated and updated to a final form. It's time for the design phase to begin - we start by creating a style-scape that proposes the design direction. But we usually also design the Homepage, as this is the most relevant page for new users. We then design page by page, for desktop and devices.

Implement designs

On the implementation phase, technical issues such as frameworks and tools to be used are already agreed. The development begins by planning the phase into sprints and tasks and including them in milestones. The product owner is periodically informed about the progress.

Test implementation

Once the tasks in a sprint are implemented, we start testing those so we make sure to keep a tight eye on the development of the project. That allows us to spot bugs and potential larger issues. Periodically, we make regression-testing to ensure project integrity. At the end of the implementation phase, there is detailed testing regarding the user interface and website functionality. 

Deliver and launch project

We deliver the project to the product owner and launch it only after all the bugs and issues that we found on the test phase are fully solved. Launching the project implies our full assistance and support.

Post-launch maintenance

Our default workflow includes one month of support for the product owner. In this period, we set up periodic meetings to instruct the product team on how to use the website, as well as provide answers to all the questions that might appear. After this period we can also set up a contract for maintenance services.

The websites we build are different from one to another. And not only in terms of product-owning or type of website but also regarding the project status and needs. There are websites that need building from scratch while other websites need additional features.

Creating a website from scratch

A new website is a complex work that demands walking through all the steps described above: brief, planning, user journeys, wireframes, designs, development, testing/delivering and post launching maintenance. For such a project we take each phase and break it into smaller chunks of work - we use an agile approach. This allows for tight progress follow-up and ongoing improvements.

Read our article on how we deal with new websites projects. Or, check our workflow scheme here.

10-CIRA-half_4-3

Working on an existing website

This type of project usually requires less actual time on solving the requirements. However, due to existing work that demands understanding, preservation or improving, the time rate tends to go high and the process often reaches high complexity levels.

The approach is most of the times, different and it's project-specific. The path we follow does include some common steps each time: documenting the project state and filling in the gaps, passing the project through a quality assurance session and reviewing the user experience.

Read our article on how we approach websites projects that already have a foundation. You can also check the workflow scheme here.

09a-CIRA-half_4-3

Websites that need improving

There are cases when websites owners need help with upgrading the quality of their website. These situations usually don't come with clear requirements on what should be done, but with expectations. 

This type of project has similar steps as the other types - again, it's a project-specific approach. What it's different is that we spend most of the project time assessing the website flaws and identifying solutions to eradicate the flaws and building advantages. Consultancy plays a major role in these types of projects.

06-CIRA-half_4-3
WHAT OUR CLIENTS SAY ABOUT WORKING WITH US

What we liked most when working with the erom team was their involvement in understanding what we needed. Each time they would deliver something, we knew how it would go beyond our own expectations.

Octavian Horj / Metalica Oradea SA

MetalicaOradea-OctavianHorj
We make a great team to work with mainly because of these values
Commited to deliver

The most important goal we set when starting a project is to deliver it in the predicted time, in the agreed format. We are also committed to doing our job properly so there will be times during the project development period when we will find better ways to build certain parts, but which would delay the delivering date. Or maybe we'll find a plugin that promises to suit our needs but requires extra testing. 

Any given situation that appears to interfere with the delivery goal, will be brought to discussion and we'll ask for your opinion on the matter. 

Reliable

As soon as we get to know our clients and understand their businesses, we make ourselves available for them to discuss any new idea or confusion they might encounter. We are aware that sometimes not all is known from the very beginning, so we take the time and make the efforts to walk through it together and find solutions.

Communicative and enjoying it

Being transparent about how we'll create a project is more than an option we always choose, is the settlement of a successful project. Communication is the most important context-asset within a project and we pretty much love doing it.

Experienced, solid know-how

The variety of projects we've been involved has allowed us to gain solid knowledge. We break a project into pieces and phases and make the most out of each. This alone has proved to be an amazing way of highing the quality of our work. We top it up by staying connected to the industry news and discoveries - we are curious fellows with a ton of energy.

Open minded

No matter how much experience we have won in all these years with projects, each more diverse, we are aware that there are many other projects ahead of us to teach us even more.
We encourage our clients to get involved throughout the project and share with us their ideas. We do come with our best solutions, but we are eager to debate the clients' ideas. They have a perspective we do our best to understand, but that we do not own.