Our main work is done in PHP and JavaScript, but we also use other programs and programming languages depending on the project requirements.
We are experienced in the most important PHP frameworks - Symfony, Laravel, CakePHP and JavaScript frameworks - Angular, Vue.JS, Jquery. We're also experienced with popular CMSs - WordPress, Drupal, Magento, PrestaShop, Sulu, Sylius.
Before starting work on a web project, it is essential - more than anything else - that the project brief is being discussed, debated and updated. Once the project goals, needs and expectations are defined the next thing to do is plan the project.
This means answering questions such as 'what are we doing', 'how are we doing this', 'why are we doing it like this and not like that'. At this point we draw the project timeline, with all the milestones and sprints, the tasks compiling these and the teams that will work on it.
The involvement of the product owner is part of the project success. That's because there is no one else who knows the product so well as this person. Sure, there is the project brief and there are our know-how and our team's expertise, but the product owner's insights are far more valuable as they bring a personal perspective.
This doesn't mean you'll have to spend all the time talking to us. We do have a workflow, we'll share our results with you and we ask for your insights at the right times.
The importance of a service or a product is given by how much the user for whom it was conceived really needs that item in the first place. Or how much improvement it brings in his life. It might sound like a cliche, but that is something that can get easily distorted in the process.
Every feature we build in or the way we lay down the options and arrange the information - they are all passed through the user's filters and debated until the best option is identified.
The designs we create for websites and applications are meant to communicate with the user. They are not meant to act as an online art canvas, but to show and convey messages. We do like to emboss attractive UI elements into a website and we do include strong visual play-frames here and there, but not in such way that the user forgets why he's there.
We try to balance the designs we create and put on the first place the user. We design for the user.
The way a website works it's probably the most important thing that the user will always acknowledge. Things like loading time, security issues, items behaviour or clear navigation are the ones for which a user will show the highest interest.
We use frameworks that are best suited for the projects we meet and tools that guarantee good, lasting functionality. The testing phase it's a big part of the project per se. We take the time to test ourselves our work, before delivering the final product.
We create presentation websites for start-ups and small to medium-sized companies. In this kind of project, we look to illustrate a clear company profile that acts as an online business card.
The e-commerce websites we build are using the popular CMSs - Drupal, Magento, PrestaShop. Other than complex information and details for the user, we also seek to ensure an easy management area for the product owner.
The web-applications we create usually come in a pack with a corporate website as well. A big part of our focus for this type of project goes into ensuring good functionality among devices and operating systems.
We create educational websites of different levels of complexity. These types of projects are among the most challenging ones in terms of user experience.
We create content-based websites such as news or magazines websites. Dealing with a large amount of content, it's essential for the user to have clear navigation and nice reading experience.
We create landing pages for a series of products/services like events, marketing campaigns and others. We usually create this for customers with whom we have already developed larger web projects or other types of projects (like branding or graphic design).
Working with Erom has been a very strategical relationship where I have learned so much more about myself and my business.
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.
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.
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.
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.
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.
